bhavya bojanapalli’s Post

💡 Simple Git Tips 💡 1. Use Auto-Correct for Git Commands: Git can automatically fix simple typos in commands. - git config --global help.autocorrect 1   Why It’s Useful: This is a lifesaver when you’re typing fast and accidentally mistype commands like 'git statsu' instead of 'git status', it will automatically assume the right command and wont throw error.   2. Quickly Undo the Last Commit (But Keep Changes) - git reset --soft HEAD~1   Why It’s Useful: If you accidentally commit something and realize you need to make more changes, this command lets you "uncommit" it without losing your work.   3. Revert a File to a Specific Commit - git checkout <commit-hash> -- <file-path>   Why It’s Useful: Handy when you only need to revert changes to one file instead of the entire project.   4. View Unpushed Commits - git log--branches --not --remotes   Why It’s Useful: It’s a good practice to check what hasn’t been pushed yet, especially before making a pull request or merging.   5. Clone Only the Latest Commit - git clone--depth=1 <repo-url>   Why It’s Useful: Saves time and space when you only need the most recent state of the repository.   6. Use Aliases for Common Commands  - git config --global alias.br branch --> (use git br instead of git branch) - git config --global alias.cm commit - git config --global alias.st status   Why It’s Useful: Saves time and keystrokes, making your workflow more efficient. #DevOps #Git #Github #opensource

Hi #connections Published my new blog 𝗚𝗶𝘁𝟭𝟬𝟭 on medium. Check out to learn about most basic to advanced git commands used in source code management. Follow me on medium to get more such insights. #git #code #technicalblog #medium #devops

Git - here are a few config commands you should know. Git wasn't initially built for today's developer workflows and processes. But the truth is that source code management tools haven't evolved much in the past 40 years. While some may rely on GUI tools, those tools mostly mirror Git's core concepts without offering much innovation and sometimes even creating problems (always `git pull` instead of `git fetch` and `git merge`). They can be difficult to grasp and navigate and prone to errors. Yet, I find it more straightforward to stick to the command line for most tasks. And even small changes can make a big difference. Here are a few tricks I want to share with you: - git maintenance start (adds a cron job to your config and does some things in the background - prefetch - it will make lots of things faster) - git config column.ui auto (list branches in columns) - git config branch.sort —committerdate (last commit first) - git config config gpg.format ssh (in case you want to sign commits with the same key you push with) - git config —global alias.staash ’stash —all’ (yes, git supports aliases) - git clone —filter=blob:none (make cloning fast for big repos) There are many more options, like adding colors to the terminal, changing the log format, etc. What are your thoughts? #git #sdlc #devops #cicd #softwaredevelopment

🚀 Simplified Git Essentials for Software Engineers 🚀 Overwhelmed by Git? Don't be! Here's a condensed guide to get you started and some handy resources to master it: Some good resources to Learn Git faster ☺️ 1.Git Official Documentation: git-scm.com/doc 2.GitHub Learning Lab: https://lnkd.in/dfQY6Jtp 3.Codecademy Course https://lnkd.in/dwG5_C6q 4. Pro Git: by Scott Chacon [Book] git-scm.com/book/en/v2 5. YouTube • FreeCodeCampOrg- beginer rb.gy/ljxt5s • FreeCodeCampOrg- Intermediate rb.gy/1x6mc Core Commands: git init git clone git add git commit git status git diff git checkout git reset git log git show git tag git push git pull Branching: git branch git checkout -b git merge git rebase git cherry-pick Merging: git merge git rebase Stashing: git stash git stash pop git stash list git stash apply git stash drop Remotes: git remote git remote add git remote remove git fetch git pull git push git clone --mirror Configuration: git config git global config git reset config Plumbing Commands: git cat-file git checkout-index git commit-tree git diff-tree git for-each-ref git hash-object git ls-files git ls-remote git merge-tree git read-tree git rev-parse git show-branch git show-ref git symbolic-ref git tag --list git update-ref Porcelain Commands: git blame git bisect git checkout git commit git diff git fetch git grep git log git merge git push git rebase git reset git show git tag Alias: git config --global alias.<alias> <command> Hook: git config --local core.hooksPath <path> 📚 Resources to Learn Git Faster: The #Git #SoftwareEngineering #Coding #LearnToCode #Developer #TechSkills #CareerDevelopment

✨ Top 10 Git Commands I Use Daily ✨ Here’s my go-to list of Git commands that I rely on in my day-to-day work: 🔄 git clone: Copy a repository into a new directory. 📋 git status: Display the current state of the working directory and staging area. 📥 git add: Add changes to the staging area, preparing them for a commit. ✅ git commit: Save your changes to the local repository with a message. 🚀 git push: Send your committed changes to a remote repository. 🔄 git pull: Fetch updates from a remote repository and integrate them with your local branch. 🔀 git checkout: Switch between branches or restore files from a specific commit. 🌿 git branch: Manage your branches—list, create, or delete them. ⚡ git merge: Combine changes from different branches into one. 🕒 git log: Display the commit history for the repository. 🔧 git rebase: Reapply commits on top of another base, keeping your history clean and linear. These commands are essential for managing my workflow efficiently! 💪 #DevOps #GIT #CICD #commands

In Git, every file in your repository falls into one of three states, forming the foundation of how Git tracks and manages changes: 1️⃣ 𝐔𝐧𝐭𝐫𝐚𝐜𝐤𝐞𝐝 An untracked file is any file that exists in your working directory but hasn’t been added to Git’s version control. Git is unaware of these files, so they won’t be included in commits or tracked for changes. 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: Imagine creating a new file called notes.txt in your project folder. Until you explicitly add this file to Git, it remains untracked. Running git status at this point will show the file under a section labeled "Untracked files." 𝐇𝐨𝐰 𝐭𝐨 𝐭𝐫𝐚𝐜𝐤 𝐢𝐭: Use git add notes.txt to move the file to the staged state. 2️⃣ 𝐒𝐭𝐚𝐠𝐞𝐝 A staged file is one that you’ve marked for inclusion in the next commit. This means Git knows you want this file’s current version to be saved when you commit. 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: After running git add notes.txt, the file is now staged. If you make any additional changes to the file after staging, those changes won’t be part of the next commit unless you stage it again. 𝐇𝐨𝐰 𝐭𝐨 𝐜𝐨𝐦𝐦𝐢𝐭 𝐢𝐭: Use git commit -m "Add notes file" to permanently save the staged changes to your Git history. 3️⃣ 𝐓𝐫𝐚𝐜𝐤𝐞𝐝 Tracked files are already under Git’s version control. Once you commit a file, it transitions from staged to tracked. Git will now monitor these files for changes. 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: After committing notes.txt, it becomes a tracked file. If you modify it later, Git will recognize it as "modified" and wait for you to stage the updated version for another commit. #DevOps #LearningJourney #Beginners #CloudComputing #Newsletter #DevOpsDaily #DevOpsCommunity #90DaysOfDevOps #OpenSource #Automation #TechLearning #trainwithshubham #Git #VersionControl

The latest version of Git is here! Learn about the new features, improvements to developer workflows, and the contributions from the GitLab team

Just published a new article on Git Worktrees. Discover how Git Worktrees can revolutionize your development workflow. Check it out and level up your Git skills today! 💻🚀 #Git #GitWorktrees #SoftwareDevelopment #DevOps #ProductivityHacks

12 most common Git Commands that we use 99% of the Time as a Software Developer: 1. git init: This magic spell breathes life into a new Git repository, transforming your project folder into a version-controlled wonderland. 2. git clone: Use git clone to download a complete repository from a remote server, allowing you to tinker and contribute. 3. git status: git status acts as your compass, revealing the current state of your files (modified, staged, or untracked). 4. git add: git add prepares your modified files to be part of the next commit. 5. git commit: git commit creates a snapshot of your project, capturing the added or modified files along with a meaningful commit message (choose wisely!). 6. git push: Collaboration is key! After committing, git push sends your changes to a remote repository (like GitHub) for others to access. 7. git pull: git pull fetches updates from the remote repository and merges them into your local copy. 8. git branch: git branch lets you create new branches to experiment with features without affecting the main project. 9. git checkout: git checkout allows you to seamlessly navigate between different development paths. 10. git merge: git merge integrates your feature branch with the main branch, resolving any conflicts that may arise. 11. git diff: git diff reveals the differences between files, branches, or commits. 12. git log: History buffs rejoice! git log provides a detailed chronological record of all your commits, allowing you to revisit past versions and understand project evolution. Mastering these Git commands will significantly enhance your productivity and collaboration in software development. #git #github #gitlab #gitcommand #devops #commands #learning #tcs

Hey developer. Did you already hear about git submodules? This is a git tool that lets you work in a repository inside another repository. This is very useful if you work on several repositories with common pieces. You can put all your shared features inside a common repository and then add it as a submodule inside each project using it. And better, you can work on the super-repo and sub-repo simultaneously, performing git flow and versioning appropriately. There's simple and complete documentation here: https://lnkd.in/dZT_PvYX Enjoy it, good learning. #dev #developement #git #version #cicd #devops #backend