Quick refresh of the Repository Management doc #13495
Merged
Conversation
This file contains 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
This PR seeks to update the Repository Management documentation to reflect recent practices including the following: - Reorganize the labels section. - General updates to the triage section. - Add a note about how to handle help requests. - Update common examples of labels, milestones, and projects. - Change 'backlog' to 'list'.
designsimply
added
the
[Type] Developer Documentation
youknowriad
reviewed
Jan 25, 2019
youknowriad
reviewed
Jan 25, 2019
|
Thanks, this is great 👍 |
|
Should we mention "Good First Issue" and "Good First Review" labels somewhere? |
|
Yes, please include |
Updating based on feedback received: - Be less specific about the version numbers in example milestones. - Add more guidelines about the Needs More Info label. - Mention "Good First Issue" and "Good First Review" labels.
gziolo
reviewed
Jan 29, 2019
| @@ -69,6 +71,8 @@ When reviewing issues, here are some steps you can perform: | |||
| - If the issue is missing labels, add some to better categorize it (requires proper permissions). | |||
| - If the title doesn’t communicate the issue, edit it for clarity (requires proper permissions). | |||
| - If it’s a bug report, test to confirm the report or add the `Needs Testing` label. If there is not enough information to confirm the report, add the `[Status] Needs More Info` label and ask for the details needed. | |||
| - Remove the `[Status] Needs More Info` if the author of the issue has responded with enough details. | |||
| - Close the issue with a note if it has a `[Status] Needs More Info` label but the author didn't respond in 2+ weeks. | |||
|
Added small tweaks to version |
gziolo
approved these changes
Jan 29, 2019
There was a problem hiding this comment.
Looks good speaking myself. I would defer the final 👍 based on opinions from @youknowriad, @mapk and @desrosj.
youknowriad
approved these changes
Jan 29, 2019
|
I merged this one. I would love still to see feedback on this one. We can always open a follow-up PR :) |
This was referenced Feb 4, 2019
youknowriad
pushed a commit
that referenced
this pull request
Mar 6, 2019
* Quick refresh of the Repository Management doc This PR seeks to update the Repository Management documentation to reflect recent practices including the following: - Reorganize the labels section. - General updates to the triage section. - Add a note about how to handle help requests. - Update common examples of labels, milestones, and projects. - Change 'backlog' to 'list'. * Quick refresh of the Repository Management doc Updating based on feedback received: - Be less specific about the version numbers in example milestones. - Add more guidelines about the Needs More Info label. - Mention "Good First Issue" and "Good First Review" labels. * Update repository-management.md
youknowriad
pushed a commit
that referenced
this pull request
Mar 6, 2019
* Quick refresh of the Repository Management doc This PR seeks to update the Repository Management documentation to reflect recent practices including the following: - Reorganize the labels section. - General updates to the triage section. - Add a note about how to handle help requests. - Update common examples of labels, milestones, and projects. - Change 'backlog' to 'list'. * Quick refresh of the Repository Management doc Updating based on feedback received: - Be less specific about the version numbers in example milestones. - Add more guidelines about the Needs More Info label. - Mention "Good First Issue" and "Good First Review" labels. * Update repository-management.md
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.
This PR seeks to update the Repository Management documentation to reflect recent practices including the following:
Checklist: