Basic Git & GitHub for DevOps Engineers.

Basic Git & GitHub for DevOps Engineers.

Day 8 of #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.

  1. 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 Choose Distributed Version Control Over Centralized Version Control?

The adoption of Distributed Version Control Systems (DVCS) over Centralized Version Control Systems (CVCS) has become increasingly popular for several compelling reasons:

1. Better Collaboration

In a DVCS, every developer has a complete copy of the repository, including the entire history of changes. This facilitates collaboration, as developers can work independently without the constant need to communicate with a central server.

2. Improved Speed

Local copies of the repository allow developers to commit changes and perform version control actions faster because they don't have to communicate with a central server.

3. Greater Flexibility

With a DVCS, developers can work offline and commit changes later when an internet connection is available. They can also choose to share their changes with only a subset of the team instead of pushing all changes to a central server.

4. Enhanced Security

DVCS offers enhanced data security. The repository history is stored on multiple servers and computers, making it more resistant to data loss.


Your Git Journey Begins

Now that you have a foundational understanding of Git, it's time to embark on your Git journey. Here are some tasks to get you started:


  1. Install Git on your computer: If you haven't already, download Git from the official website at Git Downloads.
  2. Create a free GitHub account: If you don't have one, sign up at GitHub. It's your portal to the world of open-source collaboration.
  3. Learn the basics of Git: Begin with the Git introduction video. This valuable resource will provide you with a comprehensive understanding of what Git is, how it works, and how to use it to track changes to files.


Now, you're well-equipped to navigate the exciting world of Git and version control. Get ready to collaborate, create, and code with confidence, knowing that every change is under control.


Thank you,

Happy Learning


To view or add a comment, sign in

Others also viewed

Explore content categories