Skip to content

Commit

Permalink
Updating the issue pr management guideline
Browse files Browse the repository at this point in the history
  • Loading branch information
maryamariyan committed Nov 27, 2019
1 parent a6cbdae commit f2ea2bd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/issues-pr-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ dotnet/runtime issues and pull requests are a shared resource. As such, it will

Here are a few of the most salient components of working well together, and the FAQ has much more detail.
## Scenarios where we all have to work together:
- All incoming issues and pull requests will be automatically labeled with an `area-*` label and an `untriaged` label.
- All incoming issues and pull requests will be automatically labeled with an `area-*` label. The bot will also assign the `untriaged` label to only issues, once they get created.
- All issues and pull requests should have exactly 1 `area-*` label.
- Issues are considered triaged when the `untriaged` label has been removed.
- When issues have `area-*` labels switched, the `untriaged` label must be added. This prevents issues being lost in a `triaged` state when they have not actually been triaged by the area owner. In the future, a bot may automatically ensure this happens.
Expand Down

0 comments on commit f2ea2bd

Please sign in to comment.