Introduction to Git and Commands

-

01. Introduction to Git

Git is officially defined as a distributed (VCS) version Control System.

It's a system that monitors changes in our project files over time. It allows us to record project changes at any time and return to a selected version of the tracked files. This method is often utilized by many to figure efficiently and collaborate on team projects, where each developer can distribute their own version of the project on their computer. Later, these individual versions of the project are also merged to suit the most version of the project.

Basically, it's a hugely popular tool for coordinating parallel work and managing projects between individuals and groups. Needless to mention, knowing the way to use Git may be an important skill for any developer today - it's definitely an excellent addition to your resume!

The version control system is the management of changes to document changes in computer programs, large websites, and other collections of information.

There are  two version control system in Github

  • The local version control system
  • Centralized &Distributed Version Control Systems          
The local version control system
  • Copy the file into another directory
  • it is so simple and also incredibly error-prone  
        


Centralized & Distributed Version Control Systems 

The next major issue that individuals encounter is that they have to collaborate with developers on other systems. Centralized version control systems were developed to deal with these issues. Examples of these systems are CVS, Subversion, and Perforce. Here there is one server that owns all the files and different servers that scan the files from that central location.

 


02. Repository 

A git store is a .git / folder within a project. This repository has the ability to store relevant data for your project. You can easily create this repository. The Github repository is the container that everything related to your project files. The code view is where you will find the repository these files may contain the project code documentation and other important files we also call this view the root of the project any changes to these files will be tracked via getting version control the readme is a special file that we recommend all repositories contain GitHub. GitHub looks for this file and helpful displays. In the below repository the readme should explain the project and point readers to helpful information within the projects, 

A few Operations & Commands

03. Initializing a repository

Create a new repository and start using your project with git. Go to the main folder of your project. Then use the cmd command in the path above, open the terminal and type the following command.

        git init


04. Checking the status

Located in your project folder, you can type the following command to check the status of your created repository.

       git status


05. Adding the file 

Type the following command to add git to all the files in your created project folder.

        git add .


06. Making Commits

commit is a short note applied to your code at a specific time. Type the following command to enter all the files here.

    git commit -m "Commit message"


07. Commit history

To view all the commits on your created project, you can use the following command.

    git log


08. Push the repository files

To push all the project files you have created, you can push all the files by pasting the link to the repository as your creation to the terminal. The following command can be used:

 git remote add origin youlink

 git push -u origin master


09. Ignore files

You can create a file named ".gitignore" in the project folder you created to override the files your project does not need. You can add files that you do not want to monitor.


10. Branches

A branch can be defined as a single timeline of your project. When you start a store and start creating commits, they are saved to the master branch. We have the ability to create, modify, merge and delete branches in this store. The following commands can be used for that.


  •  Create a branch


   git branch <new-branch-name>

  •  Change a branch

   git checkout <branch-name>

  • Merage a branch


   git merge <branch-name>

  •  Delete a branch


   git branch -d <branch-name>



Comments

Post a Comment

Popular posts from this blog

HTTP Methods

-
Image
  What is HTTP Verb? HTTP verbs are technically correct terms of request, and it communicates the action a user intends to take on specific resources related to these verbs and methods. HTTP password processing is very common. GET, POST, PUT, PATCH, DELETE, OPTIONS, and HEAD are the key HTTP most commonly used verbs used with RESTful services. HTTP GET The GET request was used to obtain information on resources and is not subject to any other means. The GET API should be malicious. This simply means that every API that makes similar requests should return the same result until the resource status of the server is changed. GET requests are made securely because they do not change the status of the resource. Example URI - HTTP GET http://www.abc.com/users HTTP POST  The HTTP POST method is used to create relevant resources. POST request methods are insecure. In this case, when two similar post requests are made, there may be two different resources related to the same informatio...
Read more

KoaJS in NodeJS

-
Image
What is KOA? Widely used server-side framework for Node.js. Koa was created by the same creators of express, another popular backend Jawa Script framework Koa provides a minimal interface for developing apps and APIs Accordingly, the creators sought to take into account all the shortcomings of the predecessor and make it more  modern and convenient  to use Extremely Lightweight Smaller footprint than any other Node.js framework including Express. Better and Thinner middleware. You have the option to extend the framework with an added module Modern Framework Koa is Built ES6+ and promotes modern JavaScript syntax Uses generators and async /await. Helps devs create apps that remain relevant over a long period of time Request and Response Koa uses a req and res object on top of the standard vanilla JS request and the response It accelerates HTTP server development by providing additional functionality Encapsulates req/res into a single object using context. This helps devs build ...
Read more

S.O.L.I.D Principles

-
Image
S.O.L.I.D  Principles  Introduction  SOLID principles are the look principle that allows us to manage most of the software design problems.  The principles are a subset of many principles by Robart C Martin S.O.L.I.D are 5 object-oriented principles that should be followed when design software   S-  Single Responsibility Principle (SRP) O- Open- Closed Principle (OCP) L- Liskov Substitution Principle (LSP) I - Interface Segregation Principle (ISP) D- Dependency Inversion Principle (DIP) Single Responsibility Principle (SRP) And that responsibility should be entirely encapsulated by the class every module or class should have responsibility for one part of the functionality provided by the software   Open-Closed Principle (OCP) Adding new classes, attributes, and methods, instead of changing the current ones or existing ones should implement any new functionality. Bertrand Meyer originated the term OCP.     Why OCP? if not followed  ...
Read more