Day8: Git and Github for DevOps

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 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 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 and its types?

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 to a previous state, revert the entire project 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 over Central 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.

Steps before implementation:

• Install git on your system ( if it's not already installed ) - Download it from the official website https://git-scm.com/downloads

• Create a free account on GitHub (If you don't have one) - Sign up at https://github.com/

Create a repo on GitHub and clone it to a local system

1. Creating a repository:

• Login to your GitHub account and click on the '+' sign at the top right corner.

• Select "New Repository" from the drop-down menu.

• Give your repository a name.

• Choose public or private depending on your GitHub plan.

• Add a description for the repository if you want.

• Click on the "Create Repository" button. Your new repository is ready for action.

1. Cloning repository to your local:

• Open your terminal or command prompt on your system.

• Use cd command to change the directory where you want to clone the repository.

• Copy the URL from the GitHub repository you created.

• Use the git clone <your_repository_url> command to clone the repository.

• If the repository is private, GitHub might ask for a username and password.

• Once the repository is cloned, you will have a copy of the GitHub repository on your local system.

Changes to a file in the repository and commit using Git

1. Changes to a file:

   • Create a file in your repository you cloned before through the text editor.

   • Use the git status command to see which file is added and left unstaged.

   • Use the git add <your_file_name> command to stage the file you created for further actions.

2. Commit changes:

   • Use the git commit -m "<commit_message>" command to commit the staged file. The file will be tracked after the commit.

Push the changes to the GitHub repository

• Use the git push command to push the changes from your local to remote repository (GitHub repository).

<Thank you for reading till THE END. Follow if this helps you somewhere>