5

I'm a newbie to Git and version control in general. How do you keep track of their coding to-do list and issues/bugs?

Note that I'm working on a private project (e-commerce website) with just 2 developers.

Ben G
  • 26,091
  • 34
  • 103
  • 170
  • This is a poll, not a question. – cdhowie Aug 15 '11 at 01:37
  • I've edited it to say "you" instead of "most". I just want to know what people do, and get an idea of best practices. – Ben G Aug 15 '11 at 01:39
  • The question still falls neatly under the [definition of questions not to ask section in the site faq](http://stackoverflow.com/faq#dontask). – cdhowie Aug 15 '11 at 02:45

3 Answers3

4

Git is not meant to be a bug tracking system, and if your need are a bit more complex than a simple "TODO" file, then you need to integrate Git with other systems.

That being said, I like to put a README at the root directory of my repo.
That way, I can have a quick description of what the branch is for.

git show myBranch:README
Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • 1
    This is excellent because it's simple and it cooperates well with `git diff`, `git blame`, etc.! – yingted Dec 10 '12 at 04:03
2

I'm late to this party but for anyone looking to track TODOs using a github app you can use http://srcoftruth.com. It's a free app that finds the TODOs in your source code on check-in and opens an issue for each found TODO, tracks it over time and closes it when the TODO is removed from the repo.

schellsan
  • 2,164
  • 1
  • 22
  • 32
2

I'm also developing standalone/in a small team and not having found anything that would not be complete overkill for my needs I came up with a small script, Git-Track to keep track of bugs/issues.

I've had some colleges test it and the resonance was positive. We work in science, most projects have only one or two developers and thus any major bug tracking solution is just way too fancy to be really useful.

Dirk
  • 21
  • 1