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

Git doesn’t track folders. This may bother us when we create empty folders as placeholders in a project—for example, an empty images folder at the beginning of a web project.

## Add a hidden file
If we need to track folders, we usually add a hidden file there. Communities often use an empty `.gitkeep` file for this purpose, but it’s not a standard. We may pick any file name to commit the file and track the folder path.

For example, if we create a folder named `images` and call `git status`, we won’t see the newly created folder. But if we put a file in this folder, we see it. We can test this with the following commands in the terminal provided below:

``` Shell
$ mkdir images
$ git status
$ touch images/.gitkeep
$ git status
```
> Here, we see the `images` file as an untracked file.  

Git doesn’t track folders. This may bother us when we create empty folders as placeholders in a project—for example, an empty images folder at the beginning of a web project.

# Add a hidden file
If we need to track folders, we usually add a hidden file there. Communities often use an empty `.gitkeep` file for this purpose, but it’s not a standard. We may pick any file name to commit the file and track the folder path.

For example, if we create a folder named `images` and call `git status`, we won’t see the newly created folder. But if we put a file in this folder, we see it. We can test this with the following commands in the terminal provided below:

``` Shell
$ mkdir images
$ git status
$ touch images/.gitkeep
$ git status
```
> Here, we see the `images` file as an untracked file.  

Learn the trick to track empty folders in Git.

Getting Started

Basic Command

Behind the Scenes

Essential Techniques

Flow Control

Remote and Collaboration

Handle Conflicts

Undo Changes

Rebase and Cherry Pick

Conclusion

Git Tracks Files, Not Folders