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

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

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

Task:

Install Git on your computer:

sudo apt-get update

sudo apt-get install git

No alt text provided for this image

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

To create a new repository on GitHub:

1. Go to github.com and log in to your account.

  1. Click the New repository button.
  2. Enter a name for your repository.
  3. Choose whether you want the repository to be public or private.
  4. Add a README file.
  5. Click the “Create repository” button.

No alt text provided for this image

To clone the repository to your local machine, follow these steps:

  1. On GitHub.com, navigate to the main page of the repository.

No alt text provided for this image

2. Above the list of files, click??Code.

3. Copy the URL for the repository.

4. Open?terminal and Change the current working directory to the location where you want the cloned directory.

5. Type?git clone, and then paste the URL you copied earlier.

git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY

No alt text provided for this image

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

1 . Create a file using vi editor.

2. git status - show the status of your git repository

No alt text provided for this image

3. git add - Moves changes from the working directory to the staging area.

Add files to git - git add <file_name>

Add all the current directory files to git - git add .

No alt text provided for this image

4. git commit - commit all the staged files to git.

git commit -m "your_commit_message"

No alt text provided for this image

Push the changes back to the repository on GitHub

You can request a list of all remote repositories that are currently connected to your local repository:

Syntax : git remote -v

No alt text provided for this image

git push - The?git push?command is used to upload local repository content to a remote repository. Pushing is how you transfer commits from your local repository to a remote repo.

Syntax : git?push?<remote>?<branch>

No alt text provided for this image


No alt text provided for this image

Thank you for taking time to read this article!

Shubham Londhe

Helping Students and Professionals build their Careers | Experience in DevOps | Python | AWS | PySpark | SQL | NoSQL | 1000+ Learners placed

1 年

keep learning, keep growing Sayali Shewale

要查看或添加评论,请登录

社区洞察

其他会员也浏览了