Skip to main content

Command Palette

Search for a command to run...

Advance Git & GitHub for DevOps Engineers.

Published
β€’2 min readβ€’View as Markdown
Advance Git & GitHub for DevOps Engineers.
N

Nikhil Patil

πŸ‘¨β€πŸ’» I love Linux & DevOps! πŸ’»

🐧 LinuxπŸ‘¨β€πŸ’» | DevOps & Cloud Enthusiast | 🌍 Azure Admin | πŸ› οΈ Ansible | πŸ“‚ Git | 🐳 Docker | πŸ”‘ OpenLDAP | πŸ–₯️ System Admin | | πŸš€ Jenkins πŸ› οΈ

🏠 Pune

🌟 I'm really into using and managing computers with Linux. I also like making things work smoothly and quickly.

πŸ“– I work with Microsoft Azure, use tools like Ansible and Git to automate tasks, and make software run in containers with Docker.

πŸ”’ I handle access and security using OpenLDAP, and I'm all about keeping systems running smoothly.

🌐 Exploring opportunities in cloud and DevOps.

πŸ“§ Get in touch: nikrpatil1997@gmail.com

πŸ“Œ Git Branching

Git branching is a way to work on different versions of a project simultaneously. Git branches are effectively a pointer to a snapshot of your changes.

πŸ“Œ Git Revert and Reset

Git revert Allows you to create a new commit that undoes the changes introduced by a previous commit without removing it from the project's history.

Git Reset is more like moving the branch pointer to a different commit. It allows you to reset the project's history to a specific commit, discarding commits after that point

πŸ“Œ What Is Git Rebase?

Git Rebase is a powerful Git command used to integrate changes from one branch into another. It allows you to modify the commit history by moving, combining, or excluding commits

πŸ“Œ What Is Git Merge?

Git Merge is a Git command used to combine changes from one branch into another. It allows you to integrate the work done in a feature branch or any other branch back into the main branch.

πŸ“Œ Task -1 Demonstrate the concept of Git Branch and Revert

Add a text file called version01.txt inside the Devops/Git/ 
with β€œThis is first feature of our application” written inside and commit the changes

version01.txt should reflect at local repo first 
followed by Remote repo for review.

1st line>> This is the bug fix in development branch
Commit this with message β€œ Added feature2 in development branch”

2nd line>> This is gadbad code
Commit this with message β€œ Added feature3 in development branch

3rd line>> This feature will gadbad everything from now.
Commit with message β€œ Added feature4 in development branch

Restore the file to a previous version where the content
should be β€œThis is the bug fix in development branch”

πŸ“Œ Task -2 Demonstrate the concept of branches with 2 or more branches

merged two branches