Skip to content

Commit 759d0ef

Browse files
authored
Re-alphabetize contrib labels
1 parent 56ccdd9 commit 759d0ef

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎Guidelines.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,9 @@ Every [hapijs](https://github.com/hapijs) repository should make generous use of
2626
- `dependency` - if the issue or pull request addresses a dependency issue, it should have the `dependency` tag. Any module that is running in production should have a version >= 1.0.0 and all of it's dependencies should follow suite.
2727
- `discussion` - this tag gets applied to issues that are ideas or requests from the community that need active input from other community members and possibly the Lead Maintainer.
2828
- `enhancement` - non-breaking changes that would generally require a bump in the minor version number.
29+
- `good first issue` - tasks that are sufficiently small and easy for new contributors to complete, and which collaborators don't mind assisting new contributors in completing.
2930
- `help wanted` - issues where the hapijs team is actively requesting community feedback should be tagged with `help wanted`. Issues like, [who is using hapi](https://github.com/hapijs/hapi/issues/1613) or [the joi bug hunt](https://github.com/hapijs/joi/issues/281) are recent examples of `help wanted` issues.
3031
- `maintenance` - tasks that are related to refactoring or other code changes that don't fix bugs or add enhancements
31-
- `good first issue` - tasks that are sufficiently small and easy for new contributors to complete, and which collaborators don't mind assisting new contributors in completing.
3232
- `non-issue` - this label is used when a user reports something that they perceive as a bug in a hapijs module but ultimately ends up being a user error. Often, issues tagged with `non-issue` will lead to updated documentation or additional validation.
3333
- `question` - generic label for user questions.
3434
- `release notes` - if the changes to a module are really broad, a new issue should be created and labeled with `release notes`. The issue should document what the changes are, how it impacts existing code and how to migrate to the next version.

0 commit comments

Comments
 (0)