Looking at what happened after a branch
Reported by Schwern | April 14th, 2011 @ 03:52 AM
Thanks a lot for gitx, I use it all the time.
One of the things I often want to know is what happened after a branch or tag. Git doesn't do this so well. GitX can do this, but the procedure is annoying.
- Select "All Branches".
- Search for the branch... but by SHA or subject.
- Highlight it.
- Clear the search so I can see everything again.
- Scroll around until I find my highlight.
A few additional features would make this and other things easier...
- Search by branch/tag
This is just handy.
- A "jump to branch" feature
This would be like viewing a branch, except it wouldn't stop at that branch. You'd still see everything just like viewing "All branches" and can scroll up to see what happened after.
This could be a separate feature and/or a preference to make viewing a branch jump to it instead. Seeing the whole context is much more useful than just from the branch head backwards. Because GitX loads so efficiently and fills in history, I rarely find it's a problem on even very large repositories. Case in point, the Perl 5 repository with 23 years of 46,000 commits loads in about 2 seconds.
- Cmd-F to search the list of commits without blanking out the rest
- Cmd-G to skip to the next one
This would work like Cmd-F/G does in most other apps, just scrolling and highlighting rather than just showing matches. This gives the equivalent of searching through "git log" on the command line where I can search but also page backward and forward to nearby commits.
The default search would be by subject, possibly also tag and branch.
These features would make it much, much easier to search and scan my git history in gitx rather than having to drop into git log. However, I realize I do a lot of repository archeology. :)