Day 8 Task: Basic Git & GitHub for DevOps Engineers

# Day 8: ?? Basic Git & GitHub for DevOps Engineers.

Welcome to Day 8 of the 90 Days of DevOps series! In today's lesson, we will dive into the fundamental concepts of Git and GitHub, two essential tools for version control and collaboration. Whether you're a developer or a DevOps engineer, understanding Git and GitHub is crucial for efficient code management and project collaboration.

• What is Git? ??

Git is a distributed version control system that allows you to track changes to files and coordinate work on those files among multiple people. It's an essential tool for software development but can be used for managing changes to any set of files. With Git, you can:

- Keep a record of who made changes to which part of a file.

- Revert back to earlier versions of a file when needed.

- Collaborate with others efficiently by sharing and merging changes into a single version.

• What is GitHub? ??

GitHub is a web-based platform that provides hosting for version control using Git. It extends the functionality of Git by adding features like issue tracking, pull requests, and collaboration tools. GitHub is widely popular among developers for sharing and collaborating on projects. It's also commonly used for hosting open-source projects.

• What is Version Control? ?

Version control is a system that tracks changes to files over time. It allows you to recall specific versions later, revert files to previous states, compare changes, identify contributors, and more. There are two main types of version control systems:

1. Centralized Version Control Systems (CVCS): CVCS stores all versions of a project's files on a central server. Developers check out files, make changes, and check them back in. Examples include Subversion and Perforce.

2. Distributed Version Control Systems (DVCS): DVCS allows developers to clone the entire repository, including the entire version history. This means they have a complete local copy of the repository, including all branches and past versions. Examples include Git, Mercurial, and Darcs.

## Why Use Distributed Version Control Over Centralized Version Control? ??

DevOps engineers often prefer DVCS like Git over CVCS for several reasons:

1. Better Collaboration: In a DVCS, every developer has a full copy of the repository, making it easier to collaborate without constant communication with a central server.

2. Improved Speed: DVCS enables faster commits and version control actions as developers don't need to communicate with a central server.

3. Greater Flexibility: Developers can work offline and share changes selectively, rather than pushing all changes to a central server.

4. Enhanced Security: The decentralized nature of DVCS stores repository history on multiple servers, making it more resistant to data loss.

???Task for Day 8: ??

• Exercises: ???♂?

1. Create a new repository on GitHub and clone it to your local machine. You can do this through the GitHub web interface or by running the following command in your terminal:

git clone <repository-url>

2. Make some changes to a file in the repository and commit them to the repository using Git. Use the following commands:

git add <filename>

git commit -m "Your commit message"

3. Push the changes back to the repository on GitHub:

git push origin master

#DevOps #Git #GitHub #VersionControl #Collaboration #90DaysDevOpsChallenge #DevOpswithAWS #AWSCloud