ci: Migrate from CODEOWNERS to PullApprove for PR review management - #34814
josephperrott wants to merge 12 commits into
Conversation
7c7e2c5 to
f614417
Compare
There was a problem hiding this comment.
😞 Shouldn't we have a similar check for pullapprove?
There was a problem hiding this comment.
Yes, The plan is to do this logic/check in a follow up PR.
There was a problem hiding this comment.
Is there a tracking item in our backlog for this followup pr?
fb64a4e to
644cb77
Compare
There was a problem hiding this comment.
I have gone missing from this list for some reason (I'm still in the compiler group below)
There was a problem hiding this comment.
Sorry! I used the listing at aio/content/marketing/contributors.json to create the list and must have accidentally dropped you out of the list.
There was a problem hiding this comment.
Does this include collaborators (noticed JiaLi in the list)? If so, I'm missing too!
There was a problem hiding this comment.
The intention is for it to be a list that contains all of the usernames that are present as an owner for any of the groups defined in the file.
There was a problem hiding this comment.
@IgorMinar @josephperrott Something I’ve been wondering for a while then, can we add the Googlers and Collaborators for Universal as members on platform-server? (That would be me, @alan-agius4, @kyliau, and @manfredsteyer)
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
There was a problem hiding this comment.
Posting comments from my first pass... I also pushed a commit with some fixes I made locally.
Things we should not forget to update:
- ng-bot config to require pullapprove status (
.github/angular-robot.yml) -
docs/COMMITTER.mdwhich makes references to codeowners -
docs/TRIAGE_AND_LABELS.mdwhich also makes references to codeowners - what to do with existing gh groups? delete them?
There was a problem hiding this comment.
Is there a tracking item in our backlog for this followup pr?
There was a problem hiding this comment.
contains_any_globs is an odd name. shouldn't it be matches_any_globs?
also what is files in this context? the files modified by the PR?
There was a problem hiding this comment.
matches_any_globs probably makes more sense, but is not the name of the method that they went with. I think it comes from a consistency in naming conventions with there other matcher methods.
Yes, all of the files modified in the PR.
There was a problem hiding this comment.
can you leave a comment explaining how this works? why active groups?
|
@josephperrott can you please review my commit + rebase this? thanks |
josephperrott
left a comment
There was a problem hiding this comment.
Created #34956 for the verify-codeownership followup.
d767544 to
9e142e0
Compare
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
We are migrating to PullApprove for our PR review management in an attempt to allow for more granular and equitable code review assignments across the team. Currently this migration is equivalent in the review assignments it will create. Once stable, our expectation is that we will be able to take advantage of PullApproves additional features for things like staged reviews.
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
IgorMinar
left a comment
There was a problem hiding this comment.
I've rebased this and pushed a last set of fixup commits. I think this is good to go.
I'm marking this as "blocked" so that it is merged only once @josephperrott is around to babysit this PR and ensure that it doesn't break the world. 😄
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
…34814) We are migrating to PullApprove for our PR review management in an attempt to allow for more granular and equitable code review assignments across the team. Currently this migration is equivalent in the review assignments it will create. Once stable, our expectation is that we will be able to take advantage of PullApproves additional features for things like staged reviews. PR Close #34814
|
live long and prosper pullaprove 🖖 |
This is a follow-up to angular#34814 to fix some typos in patterns and make them more similar to the old patterns from `.github/CODEOWNERS`.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |


We are migrating to PullApprove for our PR review management in an attempt
to allow for more granular and equitable code review assignments across the
team. Currently this migration is equivalent in the review assignments
it will create. Once stable, our expectation is that we will be able to
take advantage of PullApprove's additional features for things like staged
reviews.