Basic Git & GitHub for DevOps Engineers.

✅What is Git?

Git is a version control system that allows you to track changes to files and coordinate work on those files among multiple people. It is commonly used for software development, but it can be used to track changes to any set of files.

With Git, you can keep a record of who made changes to what part of a file, and you can revert back to earlier versions of the file if needed. Git also makes it easy to collaborate with others, as you can share changes and merge the changes made by different people into a single version of a file.

✅What is GitHub?

GitHub is a web-based platform that provides hosting for version control using Git. It is a subsidiary of Microsoft, and it offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. GitHub is a very popular platform for developers to share and collaborate on projects, and it is also used for hosting open-source projects.

✅What is Version Control? How many types of version controls do we have?

Version control is a system that tracks changes to a file or set of files over time so that you can recall specific versions later. It allows you to revert files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more.

There are two main types of version control systems: centralized version control systems and distributed version control systems.

1. A centralized version control system (CVCS) uses a central server to store all the versions of a project's files. Developers "check out" files from the central server, make changes, and then "check in" the updated files. Examples of CVCS include Subversion and Perforce.

2. A distributed version control system (DVCS) allows developers to "clone" an entire repository, including the entire version history of the project. This means that they have a complete local copy of the repository, including all branches and past versions. Developers can work independently and then later merge their changes back into the main repository. Examples of DVCS include Git, Mercurial, and Darcs.

✅Why do we use distributed version control over centralized version control?

1. Better collaboration: In a DVCS, every developer has a full copy of the repository, including the entire history of all changes. This makes it easier for developers to work together, as they don't have to constantly communicate with a central server to commit their changes or to see the changes made by others.

2. Improved speed: Because developers have a local copy of the repository, they can commit their changes and perform other version control actions faster, as they don't have to communicate with a central server.

3. Greater flexibility: With a DVCS, developers can work offline and commit their changes later when they do have an internet connection. They can also choose to share their changes with only a subset of the team, rather than pushing all of their changes to a central server.

4. Enhanced security: In a DVCS, the repository history is stored on multiple servers and computers, which makes it more resistant to data loss. If the central server in a CVCS goes down or the repository becomes corrupted, it can be difficult to recover the lost data.

Overall, the decentralized nature of a DVCS allows for greater collaboration, flexibility, and security, making it a popular choice for many teams.

✅Install Git on your computer

Create a free account on GitHub. You can sign up at

1️⃣ Open your web browser and go to https://github.com/

2️⃣ Log in to your GitHub account.

3️⃣ Click the "+" icon at the top-right corner, and select "New repository" option.

✅Create a new repository on GitHub and clone it to your local machine

1. 

Exercise 2: Make some changes to a file in the repository and commit them to the repository using Git

1. Move to the local repository directory

   

   ✅Make some changes to a file in the repository and commit them to the repository using Git

2. Create a text file and check the git status of

   

   

   

3. Add untacked file to the staging area by using the command 'git add <filename>' or 'git add .'

   

4. Commit the changes with a meaningful message by using the command 'git commit -m <"commit msg">'

   

   Committed successfully but push to Github you need to Configure your git username and email id and check details.

5. 

✅How do I see what was done? Viewing project history

At any point, you can view the history of your changes using

$ git log

✅Push the changes back to the repository on GitHub

Push the changes back to the repository on GitHub by using the command 'git push -u origin main'

Before pushing the code to the main branch, you need password , But if u give password to then you chance to lose your account as well as your project, then best choice is to generate Personal Access Token (PAT) and copy the token and save it somewhere else.
You can go to settings in your Github account >> Developer settings >> Personal access token >> Tokens (classic) >> Generate new token.

Once you are ready with the token go to your terminal verify and execute the push command. You will be redirected to a popup as shown in the image below:

Before pushing repository look like

BO🎇O🎇M ✨

✅📍Conclusion 🎉

Get out of your comfort zone and embrace version control.

Thanks for reading and learning 🙂