Live data from Hacker News

How we organize GitHub issues: A simple styleguide for tagging

robinpowered.com

1–10 of 16 posts

Re: How we organize GitHub issues: A simple styleguide for tagging

#5
post #4

Great stuff. I personally find it useful to have an additional "Regression" label to tag bug reports that have cropped up as a result of new work (this happens surprisingly often).

That's a smart one -- I may have to steal it. Other one I didn't mentioned was for our API we have a "Problem" tag for BC breaks.

Re: How we organize GitHub issues: A simple styleguide for tagging

#7
On a related note, I sure wish git supported labels for commits. As it stands I have started to use github-style labels in commit messages, e.g. `:bug:`, which is nice in that github will render these with icons, if supported. Unfortunately that don't have icons for many of the labels one would want to use. I've asked github a half-dozen times to add them, but to no avail :-(

Re: How we organize GitHub issues: A simple styleguide for tagging

#9
post #8

Before the end of the day, someone is going to make a GitHub app that automatically makes these labels for you.

Had been thinking about a script that will bootstrap a new github repository with relevant labels & milestones (backlog, icebox, etc)

Re: How we organize GitHub issues: A simple styleguide for tagging

#10
post #8

Before the end of the day, someone is going to make a GitHub app that automatically makes these labels for you.

It happened.

https://gist.github.com/omegahm/28d87a4e1411c030aa89

via https://robinpowered.com/blog/best-practice-system-for-organ...

Post reply on HN