GIT Commands reference for DevOps Engineer

By Anonymous -
Dear DevOps Engineer!! this post is full of experimenting with git commands running most of them on the 'Git Bash' window in my laptop. I've collected three things about each git command.
  • git command syntax
  • What this git command will do - short descriptions
  • An example command that I've executed
  • Screenshot of that command execution

How do I Start a Fresh repository in Git CLI(local repo)?

You need to create a folder where you would like to start your coding project. The code can be web-site related where you can have multiple directories involved such as HTML files into a folder, all images to be used in the website in a folder, CSS files into a folder, etc. First, make the folder structure for you project then at the root of the project need to initialize the project.  To create empty repo or re-initializing a repo

How to start a project repo in Git?

The `git init` command initiates the project in git cli.

Syntax :
git init
Note: It is always better to have a fresh directory created and then run the above command to initialize a local Git repository.

git init example



Getting a remote repository to your git client - Local system/Laptop

You can have the remote repository either public or private teams on the following SCM clouds:
  1. GitHub 
  2. GitLab
  3. BitBucket

git clone 

Syntax:

git clone ssh://git@github.com/[username]/[repository-name].git

Create a local copy of a remote repository of GitHub or Gitlab. Make sure that you're doing first time in that folder, it should not have the same repo that means if your re-run the same command it cannot work.



Please make sure you have the correct access rights, and the remote repository exists

Example of using gitlab URL:
 git clone https://github.com/BhavaniShekhar/vtdevops2021feb.git
Vybhava : git clone 


How to make permanent the code changes?

git commit 

The `git commit` command will help us to store the changes into the local repository. If you have to repository cloned or forked to your project you can do the required changes as per your feature or enhancements. After using git add we will use git commit it always requires a message that can be two parts - title and description. Mostly from the CLI commit command will be used single message. 
  • The commit message must follow few rules - it should not exceed 72 chars. 
  • The message always talks about why this commit - purpose we need to mention
  • This message should be in presentence - Not past tense nor feature tense
  •  Bug fix message must include the bug number/JIRA ticket
Syntax:
git commit -m "[commit message]"
commit changes

Example for git commit: 
git commit -m "adds sample python code"

How to deal with branches, file restoration with git command?

git checkout

The    `git checkout` command will be used generally for switching between branches, get the latest updates from the remote server when there is git fetch used. And it is also used for restore the file from previously committed version of your code. Later this command is changed to `git restore` command in the latest version of Git.

Syntax: 
git checkout -b [branch name origin/[branch name]

Clone a remote branch and switch to it
Example: 
git checkout -b feature2
Differences between git checkout & switch command

Syntax: 
git checkout [branch name]

Switch to a branch
Example: 
git checkout
git checkout command
Syntax : 
git checkout -

Switch to the branch last checked out
Example : 
git checkout -
git last checkout command
Syntax: 
git checkout -- [file-name.txt]

Discard changes to a file on which you are worked recently.
Example:


Syntax:


git push origin [branch name]



push to a branch to your remote repository

 Example: 



git push origin slave






git push command



Syntax: 


git push -u origin [branch name]



push changes to remote repository (and remember the branch)

Example: 



git push -u origin feature1






git push origin command



Syntax: 


git push



push changes to remote repository (remembered branch)

Example: 



git push






git push command 



Syntax: 


git push origin --delete [branch name]



delete a remote branch

 Example: 



git push origin --delete feature3






git remote branch delete oush command





git pull command

Syntax:


git pull origin [branch name]



update local repository to the newest commit

Example: 



git pull






git pull command






pull changes from remote repository

Example: 



git pull origin newbranch2




git remote
 
Syntax: 


git remote add origin ssh://git@github.com/[username]/[repository-name].git
    or
 git remote set-url origin ssh://git@github.com/[username]/[repository-name].git



add a remote repository

Example 1: 



git remote add origin git@gitlab.com:gitops4/docker-exercises.git




set a repository's origin branch to ssh
Example 2:



git remote set-url origin git@gitlab.com:gitops4/docker-exercises.git




git log
 
The syntax for the git log command is:


git log [--summary] [--oneline]





view changes



Example:


git log








git log command




view changes made to files or directory in (detailed)

Example: 



    git log --summary

    




git log summary command





view changes(briefly)

Example: 



    git log --oneline

    




git log oneline command




Syntax: 


git diff [source branch] [target branch]



preview changes before merging 

References: 
 Git log command examples https://www.thegeekstuff.com/2014/04/git-log/
















































Comments








Post a Comment
























Popular posts from this blog









Ansible Jinja2 Templates: A Complete Guide with Examples







By







-














Image







Here I'm starting this post with famous ARISTOTLE quote. "We are what we repeatedly do. Excellence, then is not an act, but a Habit" Welcome back Ansible Automations  and who are habituated as Ansible automation specialists this post for them to give boosted walk through, In this post, I would like to share my experiments with Jinja2 templates usage on the Ansible playbook. Of-course Jinja is from Japan it is world famous for templatization capabilities badvanced Ansible templating techniquesy integrating with multiple languages such as Python, Ruby, Salt talk etc. In this post we will be cover the following topics: What is Jinja2 template do in Ansible? Template with filters Template with Lists and sets Template module in Ansible Template with Flow Control Template using Looping Template inheritance** What is Jinja2 template do in Ansible? Jinja2 is another Python library created for Flask web framework, that comes part of Ansible installation. It is special ability as i...








Read more










Ansible 11 The uri module with examples







By







-














Image







 Hey DevSecOps Automation specialist, Welcome back to the DevOps Hunter blog. In this post, I made it for learning more about all possible parameters that we can use when an application validation is done with the Ansible 'uri' module.  Why uri module? Web Application returns status HTTPCode 200 for success, 404 for failures, and also for 503 for Server internal issues. When you work on the restart of a web application we need to know the status of the application to proceed with the next move. So this uri module is most important for reboot and restart of web applications using ansible. The uri module parameters Supported parameters include: attributes, backup, body, body_format, client_cert, client_key,        content, creates, delimiter, dest, directory_mode, follow, follow_redirects, force, force_basic_auth,        group, headers, http_agent, method, mode, owner, regexp, remote_src, removes, return_content,        selevel, serole, setype, seuser, src, status_code, timeout,...








Read more










DevOps Weapons







By







-














Image







       To achieve faster application delivery and stable environments, the right tools must be used in DevOps environments. There is no single tool that fits all your needs such as server provisioning, configuration management, automated builds, code deployments, and monitoring. Many factors determine the use of a particular tool in your infrastructure.     In this article, we will look into core tools which can be used in a typical Devops environment.     Version Control Tools:   Git  - An awesome tool to version your source code and collaborate.   Terraform  - A tool used in building, changing, and versioning the infrastructure across platforms.       Build Orchestration/Continuous Integration Tools:  Jenkins - It is an open-source, lightweight CI tool written in Java, with high extensibility and a fast release cycle.  Buildbot  - An open-source framework for automating software build, test and release process.  CruiseControl  - A CI server written in  # Ruby ...








Read more