by Nick Quaranto
With git 2.6 it’s now easier than ever to keep track of your work during an interactive rebase.
Previously, if you were rebasing interactively and had hit a conflict or stopped to reword a commit, git status would look like this:
$ git rebase -i HEAD~5
$ git status
rebase in progress; onto 0927cd6
You are currently rebasing branch ‘t…
Read More »
smartly save stashesremote tracking branchesignoring doesn’t remove a filewhere to find the git communityfinding who committed whatwhat git is nothow git stores your dataconverting from svntaggingpush and delete remote branchesinstalling gitbranching and mergingpushing and pullingignoring filesthe staging areacleaning up untracked filesreverting filesstashing your changes
interactive rebase statusfind unmerged commitsfind ancestor commitsrestoring a directory from historyrolling back changes with revertpick out individual commitsget a file from a specific revisiontemporarily ignoring fileslist remote brancheseasily fetching upstream changesreflog, your safety nethelpful command aliasesintro to rebasefinding what has been changedexporting your repositorytext-based graphsharing your changescount your commitsinteractive addingvisualizing your repocheckout tracked remote branch
gpg-sign releasesribbon/catchup: reading new commitstig, the ncurses front-end to Gitwhat’s inside your .git directoryreorder commits with rebaseeasily manage git remote brancheskeep either file in merge conflictsconvert git-svn tag branches to real tagspull with rebasesquashing commits with rebasebash auto completionpush to only bare repositorieszsh git statusbash git statusbend logs to your willrestoring lost commitspiecemeal stagingfixing broken commit messages