Another git command I love using is `git add -p`. I always want to commit in chunks as I go but sometimes I wait to long or realize later I could have broken it up. Being able to select only pieces of a file to add to a specific commit is so great. Editing the chunks manually can be a bit intimidating but since it only stages the change you can always restore the file and try again if the diff doesn't look right afte…
Git rebase -i is not that scary
21–30 of 155 posts
Re: Git rebase -i is not that scary
#22That “-I” really needs to be lowercase.
Re: Git rebase -i is not that scary
#23Re: Git rebase -i is not that scary
#24Here's a GIF I found with Google: https://yogwang.site/2025/cursor-vscode-gitlens-rebase-edito...
Re: Git rebase -i is not that scary
#25Re: Git rebase -i is not that scary
#26 git commit —fixup=
git rebase -i —autosquash
This is my best friendRe: Git rebase -i is not that scary
#27Re: Git rebase -i is not that scary
#28git commit —fixup= git rebase -i —autosquash This is my best friend
git history fixup
https://git-scm.com/docs/git-history#Documentation/git-histo...Re: Git rebase -i is not that scary
#29I still make a throwaway branch before a complicated rebase. It costs nothing and turns the whole operation into a low-stakes edit instead of a leap of faith.
Re: Git rebase -i is not that scary
#30Another git command I love using is `git add -p`. I always want to commit in chunks as I go but sometimes I wait to long or realize later I could have broken it up. Being able to select only pieces of a file to add to a specific commit is so great. Editing the chunks manually can be a bit intimidating but since it only stages the change you can always restore the file and try again if the diff doesn't look right afte…
That "git add -p" works from the command line is cool, but this is the one git task that I feel is significantly easier using a GUI tool (I use one specifically for this (and viewing diffs) while otherwise mostly using the command line).
Again, though, I still use a visual tool.