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

## Get the experimental branch

Since your `alicelib` submodule is a straightforward clone of the remote `alicelib` `origin`, you have the `master` branch and the `origin`’s `experimental` branch:

```Shell
1	cd alicelib
2	git branch -a -vv
```

You are on the `master` branch (current `HEAD` location is indicated with a `*`), which is mapped to `remotes/origin/master`.

> **References Will Be Different**<br>
The refs (e.g., `ff75b7f`) will be different in your output.

You do not have an `experimental` branch locally. However, if you check out a branch that does _not_ exist locally but _does_ exist remotely, Git will assume you want to track that remote branch.

```Shell
3	git checkout experimental
4	git branch -a -vv
```

> **More Than One Remote With The Same Branch?**<br>
If more than one remote has the same name, Git will not perform this matching. In that case, you would have to run the full command that follows.

Alternatively, you could track a completely different branch if you specify it:

```Shell
5	git checkout -b alicemaster --track origin/master
```

This is, assuming it’s the `origin`’s `master` branch that you want to track.


# Get the experimental branch

Since your `alicelib` submodule is a straightforward clone of the remote `alicelib` `origin`, you have the `master` branch and the `origin`’s `experimental` branch:

```Shell
1	cd alicelib
2	git branch -a -vv
```

Learn how to track the submodule's state.

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

Git Tracks the Submodule’s State

Get the experimental branch