Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upStyleguide for tagging #39
Comments
bmpvieira
added
the
chore
label
Mar 29, 2017
bmpvieira
added this to Backlog
in Bionode Project Board
Mar 29, 2017
This comment has been minimized.
This comment has been minimized.
Rudani
self-assigned this
Apr 7, 2017
bmpvieira
moved this from Backlog
to In Progress
in Bionode Project Board
Apr 7, 2017
bmpvieira
referenced this issue
May 24, 2017
Closed
Mozilla's Global Sprint (June 1st and 2nd 2017) #44
bmpvieira
added
the
mozsprint
label
May 30, 2017
bmpvieira
moved this from In Progress
to Next
in Bionode Project Board
Aug 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bmpvieira commentedMar 29, 2017
•
edited
For a more productive organisation, we should probably follow this simple styleguide for tagging issues and avoid creating new tags.
Here's what we should use
For clarity, use only one of these labels! if you feel that you need to use more, your issue might not be specific enough:
#EE3F46Problems (high priority):bugsecurityproduction#5EBEFFImprovements (generally iteration on code):enhancementoptimizationrefactor#91CA55Additions (generally new code):feature#CC317CFeedback (some do not involve code):discussionquestioncommunity#FAD8C7Testing (needs to be done or only occurs in):teststaging#FFC274Experience (more artistic):designux#FEF2C0Mindless (can be done during a break):chorelegaldocumentationexamples#D2DAE1Inactive (gets immediately closed):invalidwontfixduplicatedeprecatedThese can be attached to the ones above to give more context:
#BFD4F2Platform (can exceptionally be customized to group issues):serverbrowser#FBCA04Pending (stalled by difficulty or external):help wantedin progressepicon holdWe should use something like github-labels to do this automatically and integrate with #23.