Vaishnavi Shivde's blog
Day 8 Task: Basic Git & GitHub for DevOps Engineers.

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

Vaishnavi Shivde's photo
Vaishnavi Shivde
·

4 min read

In today's world of collaborative software development, Version Control Systems (VCS) have become an indispensable tool. Whether you're a seasoned developer or just starting your coding journey, understanding the fundamentals of version control is crucial. In this blog post, we'll explore what version control systems are, the types available, delve into the differences between Centralized and Distributed systems, demystify Git and GitHub, and even provide some hands-on exercises to get you started!

📝 What is a Version Control System?

Version Control System (VCS) is a tool that manages changes to documents, programs, and other collections of information. It allows multiple people to collaborate on projects simultaneously without fear of overwriting each other's work. Key features of VCS include:

  • Tracking changes made to files over time

  • Reverting to previous versions if necessary

  • Branching and merging for parallel development

🔄 Types of Version Control Systems

There are two main types of VCS: Centralized and Distributed.

  • Centralized Version Control Systems (CVCS):

    • A single, central repository stores all versions of a project.

    • Users must be connected to the central server to work on files.

    • Examples include CVS (Concurrent Versions System) and SVN (Subversion).

  • Distributed Version Control Systems (DVCS):

    • Every user has a complete copy of the repository, including its history.

    • Users can work offline and synchronize changes with others' repositories.

    • Git and Mercurial are popular examples of DVCS.

🌐 Centralized vs. Distributed Version Control

The main difference between CVCS and DVCS lies in how they manage repositories:

  • Centralized VCS:

    • Requires a constant connection to a central server.

    • Collaboration relies heavily on network availability.

    • Risk of a single point of failure with the central server.

  • Distributed VCS:

    • Allows for offline work and branching without network access.

    • Each user has a complete copy of the repository.

    • Enhanced collaboration and flexibility.

🐱 What is Git?

Git is the most widely used Distributed Version Control System today. Developed by Linus Torvalds in 2005, Git offers speed, data integrity, and support for distributed, nonlinear workflows. Its three-stage architecture includes:

  1. Working Directory: Where files are modified, added, or deleted.

  2. Staging Area (Index): Acts as a buffer between the working directory and the repository, allowing users to selectively stage changes before committing.

  3. Repository (HEAD): Stores committed snapshots of the project's history.

💼 What is GitHub?

GitHub is a web-based hosting service for Git repositories. It adds a layer of collaboration and social networking features to Git, making it easier for teams to work together on projects. Key features of GitHub include:

  • Repository Hosting: Store your Git repositories online.

  • Collaboration Tools: Issues, pull requests, and project management tools streamline teamwork.

  • Community Engagement: Follow other users, star repositories, and contribute to open-source projects.

🤔 Difference between Git and GitHub

While Git and GitHub are often used together, they serve different purposes:

  • Git:

    • Version control system software.

    • Used for tracking changes to files and managing project history.

  • GitHub:

    • A platform built around Git.

    • Offers hosting for Git repositories, collaboration tools, and social features.

🏋️‍♀️ Exercises

Ready to dive in? Here are some exercises to get you started with Git and GitHub:

  1. Create a new repository on GitHub and clone it to your local machine./

    1. Sign in to GitHub: If you don't have an account, sign up—it's free!

    2. Navigate to Your Dashboard: Once logged in, click on the "+" icon in the top right corner and select "New repository."

    3. Fill in Repository Details: Give your repository a name, optional description, choose visibility (public or private), and add a README file if needed.

    4. Create Repository: Click the "Create repository" button, and voila! Your repository is born.

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

    1. Open Terminal (or Git Bash on Windows): Navigate to the directory where you want to clone the repository.

    2. Clone the Repository: Use the git clone command followed by the repository URL.

    3. Navigate to Cloned Repository: Use the cd command to move into the newly cloned repository directory.

    4. Make Changes: Open files in your favorite text editor, make modifications, and save the changes.

    5. Stage Changes: Use git add . to stage all changes or git add <file> to stage specific files.

    6. Commit Changes: Commit staged changes with a descriptive message using the git commit command.

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

    1. Push Changes: Push committed changes to the GitHub repository using the git push command.

    2. Enter Credentials: If prompted, enter your GitHub username and password.

    3. Refresh Repository Page: Head back to your GitHub repository page, and you'll see your changes reflected.

Mastering version control is essential for any developer's toolkit. With the right understanding and practice, you'll streamline your workflow, collaborate more effectively, and become a more efficient coder. Happy coding!

Now, it's your turn. Take the exercises for a spin and start your journey towards version control mastery! 🚀

#TWSTrainWithShubham#shubhamLondheGitHubGitBasic Git & GitHub for DevOps Engineers.