Search for a command to run...
I am curious kid on the web, trying to learn more about life and other things. I enjoy building things and my medium of expression is mostly code. I have been dabbling with OpenEdx recently. I love to talk about distributed system, I have taken up learning Rust recently and been writing Python, Golang and JavaScript for a while.
No comments yet. Be the first to comment.
Reverse-engineering a ₹2,000 Wi-Fi toy drone to understand its firmware, protocols, and limits.
This year was full of surprises, mostly pleasant ones; the year was filled with friendships and travels. Towards the end of last year, Anirudha and I started working on Rust and tried picking it up. He started a project called Feluda, and I started c...
What to Remember from PyCon India 2024
Get More Done: Discover the Magic of Tiling Window Managers
Understanding SSL Certificates: Enhancing Security and Trust Online
"Woah!" this was my reaction when I discovered the --fixup flag for git commit command. It reduces the time spent on working on features/fixes by:
Avoiding temporary commit messages.
Eliminating the time taken to remove the temporary commit messages.
Helping with organized rebases.
Helping with quicker squashing of commits.
Let me walk you through the old workflow that I used to employ when I worked on any feature/fixes. I generally start with a fresh branch from the main branch.
git checkout -b farhaan/great-looking-feature
Then I will keep working on the branch and keep adding the commits. The commits are a result of a review or some additional fixes. Once the review is completed I need to squash the commits. The difficulties I face here are:
If I have done multiple fixes by any chance I will not be able to segregate them.
I need to count the number of commits to pass it to HEAD~<number> for interactive rebase.
Hence, when my work on the feature branch is done I would have to first squash my commits and then rebase the branch over main. Suppose I have 5 commits to squash I will have to run:
git rebase -i HEAD~5
There will be an editor window that will open and we need to select the commit to squash or to pick. Then there will be an editor window to modify the commit message if you want to.
All the above problems and steps are easily fixed and simplified by the --fix-up workflow. Here I put all the effort that I need into writing my first commit messages then later messages are prefixed by fixup. I can even segregate my changes into multiple commit messages. Let me show an example:
To add a fixup commit I need to give the commit hash that I want to fixup.
git commit --fixup=632aa92e0d27332b4d7caf70eb268a23d3544610
This adds the commit message fixup! First commit [feat]. Now, if we want to squash the commit message we need to autosquash .
git rebase -i --autosquash e05a9e0
We just need to be sure to give the commit hash till we want to squash.
And the result is *Drum Rolls*
I hope this workflow will help you save a lot of time and improve the way you use git. Happy Hacking!