BUGS
treelinelabs edited this page Sep 14, 2010
·
44 revisions
Bugs should be reported through Lighthouse. Please make sure that your bug hasn’t already been reported (check “solved” bugs as well).
- Component of GitX the bug occurs in (i.e.: history-view, commit-view, command-line-tool, etc)
- GitX version you’re using
- git version you’re using
- MacOS X version
- (If known) last GitX version that worked for you
- (If possible) link to the repository that causes the bug
- (If possible) commit that introduced the error (lucky guess or git bisect both work)
- GitX displays commits weird/broken since upgrading to v0.6
- Please try upgrading your git version to ≥ v1.5.6.
So, you know your way around Objective-C and/or JavaScript a little and think you can fix some simple bugs (or at least help in finding their source)? Great! Here are a few pointers what you should do:
- Always check if the bug hasn’t already been fixed, i.e. if there isn’t already a patch in master
- If you have an idea where to start looking do so!
- If you know that version x worked, but version y doesn’t anymore (i.e.: regression), then start bisecting.
- Keep your peers up-to-date on your progress, by reporting back through Lighthouse.
- You may push the branch with your bugfix(es) to GitHub if you like, but it’s not necessary. In this case it’s ok to rewind/rebase your branches as you improve your patches.
- If something was fixed by someone else, or if your patch for some reason is obsolete/unwanted, it would be nice of you to clean up your GitHub-branches, so as not to clutter the network-view.
So, to repeat: It already helps if you isolated the bug (be it by commit or by specific line/revision) but don’t know how to fix it.