Comment by fsiefken
9 years ago
I like the keep it simple approach, what would be the added value compared to keeping org-mode issue tracking files with commit and issue tags in git like having an issues.org file where time estimates, schedules, person assigned and 'date done' can be documented with tags and properties?
* TODO [#A] :f3abe64:31415: FIX bottom row space
* TODO [#B] :d4aae31:31410: BUG add miligram property
* PENDING [#A] :f4efe20:31410: FEAT implement counter
* DONE [#B] :e4bae20:31410: FEAT implement back button
with some archival function to an issues_done.org file
Well that's what I do with my little projects and it's nice that it's not tied to a VCS, but it doesn't scale (nor would this I guess). You'd have lots and lots of unnecessary commits about issues and comments in your git repo and would need to merge them etc. It's easier to set up some bug tracking system.
Would it be a pain to put it in a branch?
My git-kung is not so good, but `git worktree add ../issues` might do the trick.