Gain insights into Git version control, delving into commits, branches, and remote collaboration. Learn about resolving conflicts and handling erroneous changes to manage software projects efficiently.

MBE-  Beginning Git Version Control by Thomas Makzan.png

DockerGit.tar.gz

email

name

Grouping 

Git is one of the most widely used version control tools in the software industry. Whether working on frontend or backend, native or server-side applications, every software developer should be comfortable with Git version control.

In this course, you’ll learn how Git is used in software projects and the basics of version control. Moreover, you’ll learn commits, pushing code, branches, and Git Stash. Finally, you’ll learn to use Git for remote collaboration, including reconciling conflicts and correcting erroneous changes with fetch, pull, reversion, and cherry-picking. At each step, you’ll solve quizzes to test your knowledge.

By the end of this course, you’ll have a working knowledge of Git and its use in version control. You’ll be able to proficiently and efficiently manage your future software projects.

Getting Started with Git Version Control

## References to commits
Git manages branches by using references pointing to the commits. This mechanism allows instant branch creation without cloning the whole project folder.
## `HEAD` file
The `HEAD` file stores the current commit hash. Run the following commands in the terminal below:
``` Shell
$ ls -a
$ cd .git
$ cat HEAD
```
The command `cat HEAD` prints ref: `refs/heads/New` because we have an initial branch `master`, and then we create and check out to a branch `New`. It shows `New` since we’re currently at `New`. If we switch to master using the checkout command, it shows `ref: refs/heads/master`.





# References to commits
Git manages branches by using references pointing to the commits. This mechanism allows instant branch creation without cloning the whole project folder.
# `HEAD` file
The `HEAD` file stores the current commit hash. Run the following commands in the terminal below:
``` Shell
$ ls -a
$ cd .git
$ cat HEAD
```
The command `cat HEAD` prints ref: `refs/heads/New` because we have an initial branch `master`, and then we create and check out to a branch `New`. It shows `New` since we’re currently at `New`. If we switch to master using the checkout command, it shows `ref: refs/heads/master`.





Getting Started

Basic Command

Behind the Scenes

Essential Techniques

Flow Control

Remote and Collaboration

Handle Conflicts

Undo Changes

Rebase and Cherry Pick

Conclusion

Branches and References

References to commits

`HEAD` file