Skip to content

Comments

RFC 877: Automated Issue Triage#880

Open
kaizencc wants to merge 4 commits intomainfrom
conroy/triage
Open

RFC 877: Automated Issue Triage#880
kaizencc wants to merge 4 commits intomainfrom
conroy/triage

Conversation

@kaizencc
Copy link
Contributor

This is a request for comments about {RFC_DESCRIPTION}. See #877 for
additional details.

APIs are signed off by @mrgrain.


By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache-2.0 license

@badmintoncryer
Copy link

I think it is very favorable that this approach clarifies the criteria for which PRs are subject to maintainer review.

However, I believe most users, upon seeing that a PR has already been opened, would assume it will be merged in due course and would not think to react to the issue. For users who are unaware of this rule, we need to find a way to communicate that PRs will not be reviewed unless the corresponding issue receives reactions.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that community reviews would essentially be phased out / no longer serve their role?

Comment on lines +99 to +100
Pull requests will inherit the labels of the issue they address. Pull requests without a linked issue
are by default labeled `incubating`. We will have heavy-handed communication in the Contributing Guide

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For PRs that are not linked to an issue, would they be promoted to accepting-prs if the PR itself receives more than 5 reactions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants