Git Start for All Levels: from Begginer to Advanced

1️⃣ 𝗡𝗼 𝘁𝗼𝗼𝗹 𝗻𝗼 𝗴𝗮𝗶𝗻: Download and install Git from git-scm.com. It’s available for Windows, macOS, and Linux.

** Check out Git extension Git LFS, it uses pointers in your Git repository to track large files, replacing the actual file content with lightweight references.
2️⃣ 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻: Set up your username and email to associate with your work:

git config --global user.name "Your name"
git config --global user.email "your_email@example.com"

** Majority of the time we are using: 𝚐𝚒𝚝 𝚌𝚘𝚗𝚏𝚒𝚐 --𝚐𝚕𝚘𝚋𝚊𝚕. There is no need to write --global flag if you want to make separate configurations for every repo.

3️⃣ 𝗜𝗻𝗶𝘁𝗶𝗮𝗹𝗶𝘇𝗲 𝗮 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆: Start tracking a project with Git (on your wanted directory):

git init

** Running 𝚐𝚒𝚝 𝚒𝚗𝚒𝚝 on an existing repository doesn’t overwrite it. Instead, it simply reinitializes the .git directory. This can be helpful if your .git folder gets corrupted or if you want to recover a partially deleted Git setup

** Git allows you to customize new repositories by using templates:

git init --template=/path/to/template_directory

**A bare repository doesn’t have a working directory and is often used for remote repositories on popular tools like GitLab, GitHub:

git init --bare

4️⃣ 𝗦𝘁𝗮𝗴𝗶𝗻𝗴: Prepares and checks your changes before saving them in Git. Symbol ( . ) in this case means that we are preparing and changing all modified or created files in the directory. We are staging/preparing just in case not all changes we want to save/snapshot (later definition 𝗰𝗼𝗺𝗺𝗶𝘁):

git add .

After that you can check how repository is changed by using status command:

git status

** With 𝚐𝚒𝚝 𝚊𝚍𝚍, Git ignores files listed in .gitignore, but you can force-add them with

git add -f

** Using 𝚐𝚒𝚝 𝚜𝚝𝚊𝚝𝚞𝚜 --𝚒𝚐𝚗𝚘𝚛𝚎𝚍 shows all the ignored files, which can help you check what’s being skipped.

5️⃣ 𝗖𝗼𝗺𝗺𝗶𝘁𝗶𝗻𝗴: Process of saving changes to your local repository, capturing a snapshot of your project's current state. By providing -𝚖 (commit message) we are naming those changes that later we could easily understand what was done.

git commit -m "Created repo with multiple recipe files"

** You can use --𝚏𝚒𝚡𝚞𝚙 with git commit to mark a fix for a previous commit, then combine them with git rebase --𝚊𝚞𝚝𝚘𝚜𝚚𝚞𝚊𝚜𝚑 to streamline your commit history.

Now you know how to work locally with Git!