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

## Create repositories

To understand Git hooks properly, you’re going to create a bare repository with nothing in it and then clone from that bare repo. You looked at bare repositories earlier in [this](https://www.educative.io/courses/learn-git-hard-way/introduction-bare-repositories) (advanced) part.

```Shell
1	mkdir lgthw_hooks
2	cd lgthw_hooks
3	mkdir git_origin
4	cd git_origin
5	git init --bare
6	cd ..
7	git clone git_origin git_clone
```

You have two repositories: `git_origin` (which is the bare repository you will push to) and `git_clone` (which is the repository you will work in). You can think of them as part of a client-server Git workflow where users treat the `git_origin` folder as the server and clones as the client.


Next, add some content to the cloned repository, and push it:

```Shell
8	cd git_clone
9	echo 'first commit' > file1
10	git add file1
11	git commit -m 'adding file1'
12	git push
```
Nothing surprising should have happened there. The content was added, committed, and pushed to the origin repo.

## Adding a “pre-commit”  hook

Now imagine that you’ve set a rule for yourself that you shouldn’t work on weekends. To try and enforce this, you can use a Git hook in your clone.

Add a second change, and take a look at the `.git/hooks` folder:

```Shell
13	echo 'second change in clone' >> file1
14	ls .git/hooks
```
In the `.git/hooks` folder, there are various examples of scripts that can be run at various points in the Git content lifecycle. If you want to, take a look at them now to see what they might do, but this can be somewhat bewildering.

# Create repositories

To understand Git hooks properly, you’re going to create a bare repository with nothing in it and then clone from that bare repo. You looked at bare repositories earlier in [this](https://www.educative.io/courses/learn-git-hard-way/introduction-bare-repositories) (advanced) part.

```Shell
1	mkdir lgthw_hooks
2	cd lgthw_hooks
3	mkdir git_origin
4	cd git_origin
5	git init --bare
6	cd ..
7	git clone git_origin git_clone
```

You have two repositories: `git_origin` (which is the bare repository you will push to) and `git_clone` (which is the repository you will work in). You can think of them as part of a client-server Git workflow where users treat the `git_origin` folder as the server and clones as the client.


Next, add some content to the cloned repository, and push it:

```Shell
8	cd git_clone
9	echo 'first commit' > file1
10	git add file1
11	git commit -m 'adding file1'
12	git push
```
Nothing surprising should have happened there. The content was added, committed, and pushed to the origin repo.

# Adding a “pre-commit”  hook

Now imagine that you’ve set a rule for yourself that you shouldn’t work on weekends. To try and enforce this, you can use a Git hook in your clone.

Add a second change, and take a look at the `.git/hooks` folder:

```Shell
13	echo 'second change in clone' >> file1
14	ls .git/hooks
```
In the `.git/hooks` folder, there are various examples of scripts that can be run at various points in the Git content lifecycle. If you want to, take a look at them now to see what they might do, but this can be somewhat bewildering.

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

A ‘pre-commit’ Hook

Create repositories