Feature requests

Feature requests, like bugs, belong at Lighthouse. This page is here for purely historical reasons. If you once had a feature request here, and it is still alive, it is at Lighthouse.

Open Ideas

• Optional list of consistently-left-justified branches. My dev team has the shared branches “live”, “master” and “dev” and I’d like a preference that allows me to specify that their branch lines always be the leftmost 3 in that order. I.e., if `git branch —contains 123` emits “live”, that commit’s circle should be to the left of all other branch lines; otherwise, if it emits “master”, to the left of all other branches except live, etc. (If, say, master forks and then remerges with itself, those lines should share a color and stay between live’s and dev’s.) This would make it much easier to track shared vs. personal branches long-term, without having to follow lines with my finger.

• Also, show me a list of `git branch —contains 123` output while I’m viewing commit 123, right under the list of Parent commits.

• External diff shortcut (either keyboard, menu or both) which opens an external diff tool (probably opendiff / FileMerge by default). [pschella]

• Add proper stash listing and diffing, as well as save/pop/apply/drop. I’m fine with only supporting conflict-free stash operations. Ideally should be able to —patch with `git stash save` – ljharb

• When viewing the history of a single file, allow diffing of non-consecutive commits by selecting two commits in the History View. – [jzinn]

• Track changes to the folders/files in the repository (using fsevents or kqueue) and do a “refresh” in response to them. – [uliwitness]

• honor the “commit.template” config variable

• Magic Mouse 2-fingered swipe for next/previous commit in history view (like for next/previous email in Mail inbox). Make sure it works for 3-fingered swipes on a MacBook, too. – [rwest]

• Ignore the files listed in .gitignore in the listing of changed files. – [jammon]

• Ignore certain branches on request. best configured via a per repository config file (idea: i keep issues of my project in the same repo but do not want to have them always intertwined with my line of development in gitx).

• If the Application is installed in the Homefolder and there is a $HOME/bin folder, install the ‘gitx’ command line support there, not at /usr/local/bin — [zeisss]

• Make GitX keyboard navigatable. – niko; +1 from josh and cypok
  (As far as I can tell) these shortcuts are missing:
  • In ‘History’ view: switching panes
  • In ‘Commit’ view: switching panes, staging files, unstaging files
    • In the “Unstaged changes for #{file}” view: selecting hunks, staging hunks, unstaging hunks
    • Cmd-Return or similar invokes the Commit action

• be able to view the history of a specific blob or tree – this is very useful when I am debugging a merge and need to see how something changed — [danlucraft]

• Greater flexibility in diff format: character by character diffs, ignore whitespace diffs and wrap long lines in particular. This will make gitx much more useful for managing plain text (i.e. prose) repositories – (note that http://gitx.lighthouseapp.com/projects/17830/tickets/161-feature-request-make-diff-output-switchable-to-color-words is a part duplicate of this request) [singingfish]

• Remember file selection for tree view, add back/forward-buttons above it and make it show not just the current file but a diff to the previous version as well. Basically a “git log -p” for any file/dir in the tree. – Phil Huibonhoa and tom hirashima
  • Yes, that is certainly something we do need and high on my wish-list as well – [heipei]