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

build: avoid use of github team for dev-infra codeowner #25337

Merged
merged 1 commit into from
Jul 25, 2022

Conversation

devversion
Copy link
Member

We should just use the explicit names since there aren't a lot
of instances, and this is not changing very often.

The change back then did not bring a lot of benefits but rather made
reviews more annoying since irrelevant PRs had to be unassigned twice
to disappear in the Requested reviews view. This is because I'm
sometimes requested explicitly through other ownerships, but then also
through the dev-infra group.

Also changed the owners of goldens/ away from dev-infra since I don't know that
this is correct. Codeowners are not super strictly needed in this repo anyway..

We should just use the explicit names since there aren't a lot
of instances, and this is not changing very often.

The change back then did not bring a lot of benefits but rather made
reviews more annoying since unrelevant PRs had to be unassigned twice
to disappear in the `Requested reviews` view. This is because I'm
sometimes requested explicitly through other ownerships, but then also
through the dev-infra group.
@devversion devversion requested a review from crisbeto July 25, 2022 13:50
@devversion devversion requested review from a team, andrewseguin and jelbourn as code owners July 25, 2022 13:50
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion added action: merge The PR is ready for merge by the caretaker merge safe target: patch This PR is targeted for the next patch release target: major This PR is targeted for the next major release and removed target: patch This PR is targeted for the next patch release labels Jul 25, 2022
@devversion devversion merged commit 647737d into angular:main Jul 25, 2022
devversion added a commit that referenced this pull request Jul 25, 2022
We should just use the explicit names since there aren't a lot
of instances, and this is not changing very often.

The change back then did not bring a lot of benefits but rather made
reviews more annoying since unrelevant PRs had to be unassigned twice
to disappear in the `Requested reviews` view. This is because I'm
sometimes requested explicitly through other ownerships, but then also
through the dev-infra group.
devversion added a commit that referenced this pull request Jul 25, 2022
We should just use the explicit names since there aren't a lot
of instances, and this is not changing very often.

The change back then did not bring a lot of benefits but rather made
reviews more annoying since unrelevant PRs had to be unassigned twice
to disappear in the `Requested reviews` view. This is because I'm
sometimes requested explicitly through other ownerships, but then also
through the dev-infra group.
@devversion devversion added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Jul 25, 2022
@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 Aug 25, 2022
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants