1. 14

  2. 7

    Whenever I see a github bugtracker with half a dozen labels on each issue, I can’t help but think that they’ve reinvented Bugzilla’s Components, Bug states and resolutions, Flags, …

    1. 2

      There are a bunch of obvious useful features missing from github’s issues. GitLab is a bit better and supports sorting by priority at least.

      It also allows you to define labels at the organisation rather than project level, which is potentially useful.

      1. 3

        I have said it before, but for what it is worth: I recommend using actual bug tracking software. Github is a source code repository hosting site. Separation of concerns and all that.

        1. 3

          Github issues are fine for small projects with simple and informal workflows, but I think if you need even a single label, then you need a real bugtracker.

          Generally, if you find yourself implementing an ad hoc, unenforceable process, it may be time to look for tools that already implement it or allow implementing it in a machine-enforceable fashion.

          “Beginner-friendly” and similar may be an exception, since they have no effect on the process and are only there to help new contributors pick things to work on.

    2. 1

      Another label I found really useful was component: x to say which part of the project an issue affected.

      It would be great if there was a way to automate creating all of these labels too, because it’s a bit of a chore to go through and add a dozen issue labels to a new project.

      1. 3

        I would put component: x under tags. For me they are a “catch all” label type.

        But regarding automation of creating the labels - there is a way. Here is an example script: https://github.com/thisisarray/GitHub-Issues-Process/blob/master/set-github-labels.sh

        For it to work you will first need to get a GitHub “token”, which can be created somewhere under settings. Then simply adjust the labels to the ones you want (note you can delete and add them), and pass your username, repository, and token to the script.

      2. 0

        nice write up :)

        1. 0

          Great idea, I think I’ll be implementing something like this in my own projects.