clarifying intended issue usage #101
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
t8y8
approved these changes
Oct 25, 2016
|
|
||
| * **bug** - A bug is an unintended behavior for existing functionality. It only relates to existing functionality and the behavior that is expected with that functionality. We do not use **bug** to indicate priority. | ||
| * **enhancement** - An enhancement is a new piece of functionality and is related to the fact that new code will need to be written in order to close this issue. We do not use **enhancement** to indicate priority. | ||
| * **CLARequired** - This label is used to indicate that the contribution will require the CLA is signed before we can accept a PR. This label should not be used on Issues |
There was a problem hiding this comment.
require that the CLA is signed or require the CLA be signed
| * **enhancement** - An enhancement is a new piece of functionality and is related to the fact that new code will need to be written in order to close this issue. We do not use **enhancement** to indicate priority. | ||
| * **CLARequired** - This label is used to indicate that the contribution will require the CLA is signed before we can accept a PR. This label should not be used on Issues | ||
| * **CLANotRequired** - This label is used to indicate that the contribution does not require a CLA to be signed. This is used for minor fixes and usually around doc fixes or correcting strings. | ||
| * **help wanted** - This label on an issue indicates it's a good choice for external contributors to take on. It usually means it's an issue that can be tackled by first time contributors. |
| causing pain from our users. The short of it is, purple tags are ones that | ||
| anyone can add to an issue: | ||
|
|
||
| * **Critical** - This means that you won't be able to use the library until the issues has been resolved. If an issue is already labeled as critical, but you want to show your support for it, add +1 comment to the issue. This helps us know what issues are really impacting our users. |
| anyone can add to an issue: | ||
|
|
||
| * **Critical** - This means that you won't be able to use the library until the issues has been resolved. If an issue is already labeled as critical, but you want to show your support for it, add +1 comment to the issue. This helps us know what issues are really impacting our users. | ||
| * **Nice To Have** - This means that the issue doesn't block your usage of the library, but would make your life easier. Like with critical, if the issue is already tagged with this, but you want to show your support, add +1 comment to the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to make sure everyone is on the same page for labels, so adding a section to the contributing document that describes the intended usage of labels in this repo.