Getting Started with Git and Github


Introduction: 

Git is a simple open source version control system. It stores the information of anything with different versions. Mostly, it is used to store the source code of any application. Other version control softwares include Subversion, Bitbucket. The main use of this version control system is to store different updates of the same project with different versions at the same place. It also helps when multiple people are working on the same project but on a different aspects associated to that project. This is just a command line tool.


Github is a git repository hosting service. It is a web based graphical interface that provides version control and source code management features of Git.


Workflow of Git:

Any local repository (any project stored locally) consists of three trees maintained by git. They are:

  1. Working Directory - This holds the actual files. 
  2. Index - This acts as a staging area. This is kind of storage space between the Working Directory and Head. This is a virtual space between Working Directory and Head.
  3. Head - This the place where information from Working directory is sent after committing the code. This is kind of a virtual space between working directory and Github.

Workflow from Git to Github:

Once the information in Git is committed to Head. It can be pushed to Github using a push command.

Creating a Git project and pushing it to Github:

1. Create a Git Repository

Create a new directory/new folder.

Perform git init in the terminal.  This place acts as working directory now


2.  Add files from Working directory to Index

This step is performed only when new files are created.

Any new files created in the Working directory should be added to the index with commands:


git add *  - to add all files to the index


git add <filename> - to add particular file to index


3.  Commit/copy the code to Head

Copying the code from working repository to Head is termed as commit.

Committing the code to Head is done with the command:


git commit -m "any committing message "


Note: Before performing the 4th step, there should be an existing remote repository in Github and a connectivity to the working repository in Git and remote repository in Github should be made. 

To create a remote repository in Github, Go to your Github account and click on create new repository and give it a name. 


Now, connectivity between the Git Working directory and Github remote repository is made with the command:

git remote add origin <server url for the project- either ssh or https >


This url is obtained in the Github account. Go to your Github account. Click on the repository that you just created. Click on the clone option on the right. It has the URL for that project.



4. Push/copy the code from Git to Github


Once the information in Git is committed to Head, it can be sent/pushed to Github.

Sending the code from Git to Github is termed as push.

To push the changes to remote repository in Github, here is the command:


git push


git push origin <branch name> - to push the changes to specific branch. master is the default branch


Comments

Post a Comment

Popular posts from this blog

Getting started with Spring Boot Application and pushing it to Github

Image
Part 1: Creating a SpringBoot Application Introduction: Spring boot is an open source most popular Java Framework which provides flexibility, efficiency, security, ease to the Java Developers. Things you need: IDE JDK 1.8 or later Gradle or Maven - Don't have to install it. IntelliJ provides a default version This project is currently using IntelliJ CE as IDE, Java 11 JDK file and maven as dependency tool. Step by step process to create a simple SpringBoot Application: 1 . Open the IntelliJ IDE. Click on File -> New -> Project 2. Select the project type as Spring Initializer 3. Now, it's time to give it a name.  Group :  specifies the id of the project group. It is actually a set of directories path in which the artifact resides. Artifact : specifies the id of the project. It is actually the project name. Type : Could be maven or gradle. Let's start with a maven project. Version : Could update the version of the project. It is by default set to 0.0.1-SNAPSHOP Group a...
Read more

Spring Boot Caching

Image
Spring Boot Caching Caching: The Spring Framework provides support for transparently adding caching to an application. At its core, the abstraction applies caching to methods, thus reducing the number of executions based on the information available in the cache. EhCache: EhCache is an open-source, Java-based cache used to boost performance. The current version of Ehcache is 3. It provides the implementation of the JSR-107 cache manager. We can use it directly. First, create a spring boot hello-world   gradle project using reference: https://beginnersword.blogspot.com/2020/07/getting-started-with-spring-boot.html Implementation: Add the below gradle dependencies in the build.gradle file. Let’s create a TestCacheController in the controller package and create an endpoint named it as /testCaching . Now create a model class Test and create a variable named username, message then generate getter and setter for them. Let’s now create a service class with the name TestCacheService a...
Read more

Performance test with Gatling

Image
Introduction: Gatling is an open-source load testing tool written purely in Scala code. The straightforward and expressive DSL that Gatling offers makes it simple to write load testing scripts. It doesn’t contain a GUI (like say JMeter ), although it does ship with a GUI to assist with recording scripts. It can run a huge amount of traffic on a single computer, eliminating the need for complex distributed testing infrastructure. The Gatling code check can be checked into a version control system, and easily used with Continuous Integration tools to run load and performance tests as part of your CI build. Downloading: Download gatling from =   https://gatling.io/open-source/ Testing  Two types of testing: By using HAR file = which is handled by recorder.sh file By writing scripts =  which is handled by gatling.sh file      Location for recorder.sh = cd gatling**/bin/      Location for gatling.sh = cd gatling**/bin/ ...
Read more