forked from BellevueCollege/BellevueCollege.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Github Practices
Shawn South edited this page Feb 19, 2014
·
1 revision
This page documents the standard practices Bellevue College uses for repositories hosted on Github.
While a new repository comes with a minimal set of labels, we've established the following set to provide more comprehensive identification and categorization:
-
Priority labels
- 1-Blocker (red)
- 2-Critical (orange)
- 3-Important (pink)
- 9-Low Priority (light blue)
-
Type labels - Identifies the kind of issue.
- Bug (red) - already provided
- Feature (teal) - replaces enhancement
- Task (blue) - any work that doesn't qualify as a feature request or bug - often a sub-task of one.
- Question (purple) - already provided
-
Area labels (yellow) - This category is often project-specific and is used to associate issues with a particular component of the project. Examples include core, documentation, database, etc.