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

# How can we prevent files/folders from being tracked?
Mostly, we don’t want to add everything into version control. Some files are never tracked. Generally, we would like to ignore the `build` and `output` folders. We also want to ignore the private key, passwords for databases, and secret hashes for applications.

- **Ignore files:** We can create a `.gitignore` file at the base of the project folder. The `.gitignore` file allows us to list files that we don’t want to track at all. These files won’t appear as `Untracked files` when viewing the `git status` result.

- **Ignore folders:** We can ignore an entire folder by specifying the folder name.

- **Ignore certain types of files:** We can ignore certain types of files with the wildcard character—for example, `build/*.exe`. Suppose we have five files, but we don’t want to track `file2.txt` and `file5.txt`. We make a `.gitignore` file at the root of our project folder and add the file names we want to ignore. We add and commit only `file1.txt` and `file3.txt`. So, if `.gitignore` works, only `file4.txt` should appear as an untracked file in the `git status` result and not `file2.txt` and `file5.txt`.

> **Note:** We can still force add files that are ignored using the `git add -f` option.

# Commands to be executed
Try out these commands in the terminal given below. The `.gitignore` file already contains `file2.txt` and `file5.txt`:
```Shell
$ git add file1.txt file3.txt
$ git commit -m "Initial commit with File 1 and 3"
$ git status
```

Learn to exclude files that we don’t want to track.

Getting Started

Basic Command

Behind the Scenes

Essential Techniques

Flow Control

Remote and Collaboration

Handle Conflicts

Undo Changes

Rebase and Cherry Pick

Conclusion

Ignore Files With .gitignore

How can we prevent files/folders from being tracked?