-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing "issue" creation #63
Comments
You can't explicitly prioritize in GitHub. I'd imagined we'd prioritize and group bugs (by iteration or whatever) in a document that sits apart from GitHub. But, GitHub does allow 'grouping' bugs in three ways: 'assignment' (to a person), 'milestone' (which would probably map to our iterations), and 'label'. The label is where you can assign an informal (informal in that the labels aren't a controlled - within GitHub - vocabulary) priority, but apparently there's no easy way to order on the labels. Here's a post that describes how some people use labels to manage/organize bugs, including descriptions of the label names they use: http://programmers.stackexchange.com/questions/129714/how-to-manage-github-issues-for-priority-etc This set of labels (taken from different parts of that document) might work: Category Labels (could also use all caps to visually separate) type:Task priority:High status:confirmed james On 2013-03-10, at 8:18 PM, SusanBrown [email protected] wrote:
|
Testing to see If I can create an "issue" (a misuse of the word that I loathe).
The text was updated successfully, but these errors were encountered: