Deepak Jadhav's Blog
Day 9:Getting Started with Git & GitHub part 1: Essential Tools for DevOps Engineers

Day 9:Getting Started with Git & GitHub part 1: Essential Tools for DevOps Engineers

Deepak Jadhav's photo
Deepak Jadhav
·

5 min read

🚀 Welcome to Day 9 of the DevOps 90-Day Challenge! Today, we embark on an exhilarating journey into the world of version control with Git and GitHub. Whether you're a seasoned DevOps engineer or just beginning your coding adventure, mastering Git and GitHub is essential for seamless collaboration, efficient code management, and accelerated deployment processes. Join us as we dive into the fundamentals of Git, explore the advanced features of GitHub, and discover how these powerful tools can supercharge your DevOps journey! 💻🔧🌟

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

Tasks :

  • Install Git on your computer (if it is not already installed). You can download it from the official website at https://git-scm.com/downloads

  • Create a free account on GitHub (if you don't already have one). You can sign up at https://github.com/

  • Learn the basics of Git by reading through the video This will give you an understanding of what Git is, how it works, and how to use it to track changes to files.

Lets do some practicals on Github !!!

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

  1. lets create new git repository on GitHub with name BasicsOfGit-GitHub

  1. Git_Basic.txt file has been created in BasicsOfGit-GitHub repository

  1. We copied github repo url for cloning the same repository on our local machine using below command.

    $ git clone https://github.com/deep4devops/BasicsOfGit-GitHub.git

We have successfully cloned github repository in our local system. In next blog we will deep dive into git and GitHub practicals so keep learning and stay tuned.

Conclusion: Git and GitHub are powerful tools that empower developers to collaborate, track changes, and deploy software with confidence. By understanding the basics of version control and mastering Git and GitHub, you'll unlock new levels of productivity and efficiency in your development workflow. So, keep exploring, keep learning, and embrace the power of Git and GitHub on your coding journey! #90DaysOfDevops Challenge !!🚀🔍🌟