Skip to content
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

docs: update TRIAGE_AND_LABELS.md #30171

Closed
wants to merge 7 commits into from

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Apr 27, 2019

  • Add info about who adds/removes some PR labels.
  • Document missing labels: PR action: review, PR action: rerun CI at HEAD

@gkalpak gkalpak requested a review from IgorMinar as a code owner April 27, 2019 12:29
@ngbot ngbot bot modified the milestone: needsTriage Apr 27, 2019
@gkalpak gkalpak force-pushed the docs-update-labels branch 2 times, most recently from 1694f02 to 6d49d4d Compare April 27, 2019 13:15

### `PR action: rerun CI at HEAD`
* _**Who adds it:** Anybody._
* _**Who removes it:** ???_
Copy link
Contributor

Choose a reason for hiding this comment

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

the bot should remove it automatically - @ocombe I don't think that this is the case right now. Could we change the bot to remove the label after the CI is kicked off? thanks!

Copy link
Contributor

Choose a reason for hiding this comment

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

hmm.. actually adding the label doesn't seem to trigger the CI restart right now. is there a bug somewhere?

Copy link
Contributor

Choose a reason for hiding this comment

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

The firebase config wasn't updated when the PR was merged. I cleaned it, it removes it now

Copy link
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

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

the rest looks reasonable to me, but I'll wait for others to chime in as well.

@@ -167,16 +180,32 @@ Only the `PR action: merge` label means that the PR is ready for merging.
## Special Labels

### `cla: yes`, `cla: no`
* _**Who adds it:** @googlebot._
Copy link
Contributor

@IgorMinar IgorMinar Apr 28, 2019

Choose a reason for hiding this comment

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

Suggested change
* _**Who adds it:** @googlebot._
* _**Who adds it:** @googlebot, or a Googler manually overriding the status in case the bot got it wrong._

Managed by googlebot.
Indicates whether a PR has a CLA on file for its author(s).
Only issues with `cla:yes` should be merged into master.

### `aio: preview`
* _**Who adds it:** Anybody. (Typically the author or a reviewer.)_
Copy link
Contributor

Choose a reason for hiding this comment

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

keep in mind that only org members can add labels to PRs, so "Anybody" is misleading.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd use a "team member"

Copy link
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

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

the rest looks good to me.

* _**Who adds it:** Any team member._
* _**Who removes it:** The Angular Bot, once it triggers the CI rerun._

This label can be added to instruct the Angular Bot to rerun the CI jobs for the PR at latest HEAD
Copy link
Contributor

Choose a reason for hiding this comment

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

unnecessary line break

* _**Who adds it:** Typically the PR author._
* _**Who removes it:** Whoever added it._
* `PR action: review` (optional): One or more reviews are pending. The label is optional, since the review status can be derived from GitHub's Reviewers interface.
* _**Who adds it:** Any team member. The caretaker can use it to differentiate PRs pending review from merge-ready PRs._
Copy link
Contributor

Choose a reason for hiding this comment

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

I feel this label is in a bad place. It's optional, somewhat redundant, anyone can add it, and at least 2 people are responsible for removing it. And yet it signals that there's still work (reviews) to be done, and shouldn't be merged.

I think the end result is that the label is ignored. The PR author might not know that someone added it. The reviewers might not bother to see if they are the last one and remove it. It can just stay there without anyone removing it indefinitely.

So what should the caretaker do? If they are to use their best judgement and validate it against the GH reviewers interface, what's the point of it to begin with? Might as well do without that redundant chore. If they are to respect it, then the PR author can find their PR sitting there with all reviews just because someone else decided to add the label at some point.

IMHO this label needs to be stricter or be done away with. I tend towards removing it.

Copy link
Member

Choose a reason for hiding this comment

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

One benefit of this label is that it is not possible to filter the PR list view based on whether all the reviews have been approved.

Copy link
Member Author

Choose a reason for hiding this comment

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

FWIW, I agree with @filipesilva. If there is no way for the caretaker to filter based on PRs pending reviews, we should come up with another way that can be better automated.

In any case, this PR was specifically about documenting what the label is currently used for, so 🤷‍♂

@gkalpak gkalpak added action: merge The PR is ready for merge by the caretaker and removed action: discuss labels May 21, 2019
@jasonaden jasonaden closed this in 8c00fce May 21, 2019
jasonaden pushed a commit that referenced this pull request May 21, 2019
jasonaden pushed a commit that referenced this pull request May 21, 2019
@gkalpak gkalpak deleted the docs-update-labels branch May 21, 2019 20:11
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes effort1: hours risk: low target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants