Day 8 Task: Basic Git & GitHub for DevOps Engineers. #90DaysOfDevOps

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 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 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.

Exercises:

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

  Step 1: Clone the repository from GitHub to your local machine.

  git clone <repository-url>

  step 2: Create a new branch.

  git checkout -b my-branch

  step 3: Make changes to a file in the project. For example, open the README.md file and add a new line of text.

  step 4: Stage and commit the changes.

  git add .

  git commit -m "Added a new line to README.md"

  step 5: Push the changes to the remote branch.

  git push origin my-branch

  step 6: Go to the GitHub repository and create a new pull request from the my-branch branch to the main branch.

  step 6: Review the changes in the pull request, add comments if necessary, and merge the pull request into the main branch.

  step 7: Review the changes in the pull request, add comments if necessary, and merge the pull request into the main branch.

  step 8: Finally, pull the changes from the remote main branch to your local main branch.

  git checkout main

  git pull origin main

• we have successfully created a new branch, made changes to a file, and merged the changes back into the main branch using Git and GitHub.

  stay tuned for more blogs..if you find this article useful then please hit that like button. HaPpy Learning..

  #DevOps