In this module, you will get hands-on experience working with Git and its advanced concepts.

DevOps for Developers

Git is one of the most widely used version control tools, and is something that every developer should become comfortable with. In this module, you will get hands-on experience working with Git so that when it comes time to use it, you’ll be ready.

You’ll start by learning some of the more fundamental concepts such as initializing a Git repository, adding files to a repository, and how to commit changes. You’ll also learn how to clone a repository, and how to create branching.

You’ll then make your way to some more advanced concepts like Git stash, cherry-picking, working with multiple repositories, pushing code, and a lot more.

By the end of this module, you will have a proficient and working knowledge of Git which will serve you well throughout your career.

Git and GitHub

## Add commits

First, set up a repository with two commits:
```Shell
1	mkdir lgthw_reflog
2	cd lgthw_reflog
3	git init
4	echo first commit > file1
5	git add file1
6	git commit -m "first commit"
7	echo second commit >> file1
8	git add file1
9	git commit -am 'second commit message for file1.1'
10	git log
```

## Remove commit

Then do some magic to effectively remove the last commit by entering the following commands in the terminal given above:

```Shell
10	git checkout HEAD^
11	git branch -f master
12	git checkout master
13	git log
```

> **What was that?**<br>
Don’t worry about what you just did; it’s a more advanced set of commands that mess with Git’s history. We'll cover it later.

The last commit has disappeared! You have fully reverted the `master` branch to where it was before. Even `git log --all` does not show it because it's not on a branch.

Don’t worry about the details of what you did! The point here is to create a situation in Git that you want to get out of.

## Retrieve commit

This is where Git's reflog can help.

Git reflog records all _movements_ of branches in the repository. As with `git stash`es, it is local to your repository.

```Shell
14	git reflog
```

# Add commits

First, set up a repository with two commits:
```Shell
1	mkdir lgthw_reflog
2	cd lgthw_reflog
3	git init
4	echo first commit > file1
5	git add file1
6	git commit -m "first commit"
7	echo second commit >> file1
8	git add file1
9	git commit -am 'second commit message for file1.1'
10	git log
```

# Remove commit

Then do some magic to effectively remove the last commit by entering the following commands in the terminal given above:

```Shell
10	git checkout HEAD^
11	git branch -f master
12	git checkout master
13	git log
```

> **What was that?**<br>
Don’t worry about what you just did; it’s a more advanced set of commands that mess with Git’s history. We'll cover it later.

The last commit has disappeared! You have fully reverted the `master` branch to where it was before. Even `git log --all` does not show it because it's not on a branch.

Don’t worry about the details of what you did! The point here is to create a situation in Git that you want to get out of.

# Retrieve commit

This is where Git's reflog can help.

Git reflog records all _movements_ of branches in the repository. As with `git stash`es, it is local to your repository.

```Shell
14	git reflog
```

Learn how you can remove a commit and then retrieve it.

Before We Begin

Introduction to Git

Git Basics

Clone a Repository

Git Branching

Merging

Git Stash

Git Add Interactive

Reflog

Cherry Picking

Git Rebase

Git Bisect

Fetching and Pulling Content

Working With Multiple Repositories

Pushing Code

Git Submodules

Pull Requests

Git Log

Squashing Commits

Bare Repositories

Cherry-Picking and Three-Way Merges

Git Hooks

Conclusion

Lose a Commit, Get it Back

Add commits

Remove commit