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

## Tracking a branch

More rarely, you may want to track a branch on the remote repository that has a different name. Or you may want to manually mark the local branch as tracking a specific remote one.

In these situations, you might see this kind of error when you push:

```Shell
1	git push
```

As is often the case, a careful reading of the error will tell you what you need to know. It’s just the jargon that can be difficult to follow!

In this case, the error is telling you that your branch is not tracking any remote branch, so it doesn’t know what to push to.

## Reproducing the situation

Type in these commands to reproduce this situation:
```Shell
2	rm -rf git_origin git_clone
3	mkdir git_origin
4	cd git_origin
5	git init
6	echo 'first commit' > file1
7	git add file1
8	git commit -am file1
9	cd ..
10	git clone git_origin git_clone
11	cd git_clone
12	git checkout -b abranch
13	echo 'origin abranch commit' >> file1
14	git commit -am 'cloned abranch commit'
15	git push
```

# Tracking a branch

More rarely, you may want to track a branch on the remote repository that has a different name. Or you may want to manually mark the local branch as tracking a specific remote one.

In these situations, you might see this kind of error when you push:

```Shell
1	git push
```

As is often the case, a careful reading of the error will tell you what you need to know. It’s just the jargon that can be difficult to follow!

In this case, the error is telling you that your branch is not tracking any remote branch, so it doesn’t know what to push to.

# Reproducing the situation

Type in these commands to reproduce this situation:
```Shell
2	rm -rf git_origin git_clone
3	mkdir git_origin
4	cd git_origin
5	git init
6	echo 'first commit' > file1
7	git add file1
8	git commit -am file1
9	cd ..
10	git clone git_origin git_clone
11	cd git_clone
12	git checkout -b abranch
13	echo 'origin abranch commit' >> file1
14	git commit -am 'cloned abranch commit'
15	git push
```

Learn how to track remote branches that have different names from local branches.

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

Tracking Remote Branches With Different Names

Tracking a branch