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

## What is an alias?
If a command is very long, we can set an **alias** command for it. We do this by setting the alias in the `config` file in the `.git` folder.

There are several places where we can put the `config` file. Most likely, we’ll want to create this file in our home directory. That applies to all terminals on our machine and projects under our user account.

For example, here’s an alias to show all branches with one-line log commits and graph view:

```Shell
[alias]
    st = status
    ll = log --all --oneline --graph --decorate --color
```
There are two methods by which we can set an alias. Each method is explained below.

### First method
1. In the main `SampleFolder`, run the `ls -a` command to see all the hidden files and folders. 
2. We see a folder named `.git`. Move into that folder using the `cd .git` command. 
3. Use the `ls -a` command again to see all files. 
4. Write the lines mentioned above in the `config` file using any editor or `echo` command:

   ``` Shell
   $ ls -a
   $ cd .git
   $ ls -a
   $ echo [alias] >> config
   $ echo st = status >> config
   $ echo ll = log --all --oneline --graph --decorate --color >> config
   ```

5. Next, come back to the main folder using the `cd .` command.
6. In the `SampleProject` folder, run the commands below to confirm the results:

   ``` Shell
   $ git status
   $ git st
   $ git log --all --oneline --graph --decorate --color
   $ git ll
   ```

The output of the first two and the last two commands should be consistent. If an alias isn’t made, it gives an error that no such command exists in Git.

# What is an alias?
If a command is very long, we can set an **alias** command for it. We do this by setting the alias in the `config` file in the `.git` folder.

There are several places where we can put the `config` file. Most likely, we’ll want to create this file in our home directory. That applies to all terminals on our machine and projects under our user account.

For example, here’s an alias to show all branches with one-line log commits and graph view:

```Shell
[alias]
    st = status
    ll = log --all --oneline --graph --decorate --color
```
There are two methods by which we can set an alias. Each method is explained below.

## First method
1. In the main `SampleFolder`, run the `ls -a` command to see all the hidden files and folders. 
2. We see a folder named `.git`. Move into that folder using the `cd .git` command. 
3. Use the `ls -a` command again to see all files. 
4. Write the lines mentioned above in the `config` file using any editor or `echo` command:

   ``` Shell
   $ ls -a
   $ cd .git
   $ ls -a
   $ echo [alias] >> config
   $ echo st = status >> config
   $ echo ll = log --all --oneline --graph --decorate --color >> config
   ```

5. Next, come back to the main folder using the `cd .` command.
6. In the `SampleProject` folder, run the commands below to confirm the results:

   ``` Shell
   $ git status
   $ git st
   $ git log --all --oneline --graph --decorate --color
   $ git ll
   ```

The output of the first two and the last two commands should be consistent. If an alias isn’t made, it gives an error that no such command exists 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 Alias Configuration

What is an alias?