Skip to content

build: broaden ownership to team #29199

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

Merged
merged 1 commit into from
Jun 6, 2024
Merged

Conversation

andrewseguin
Copy link
Contributor

Assigned ownership per component made more sense in the early days when we each had fully authored components

@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Jun 5, 2024
/goldens/** @andrewseguin @mmalerba @crisbeto
/src/* @devversion @josephperrott
/* @devversion @josephperrott
* @angular/components-googlers
Copy link
Member

Choose a reason for hiding this comment

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

I think you actually need to have the base directories you want to include here.

* would just refer to the files at the root of the repository

** would be everything in the repo, but that would include the other files I believe.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think * might be a special case, cause I do see that something like dir/* only covers immediate folder files (not nested). Here's what their docs say

# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @global-owner1 and @global-owner2 will be requested for
# review when someone opens a pull request.
*       @global-owner1 @global-owner2

Copy link
Member

Choose a reason for hiding this comment

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

oh okay, works for me!

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

/goldens/** @andrewseguin @mmalerba @crisbeto
/src/* @devversion @josephperrott
/* @devversion @josephperrott
* @angular/components-googlers
Copy link
Member

Choose a reason for hiding this comment

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

oh okay, works for me!

@andrewseguin andrewseguin marked this pull request as ready for review June 6, 2024 15:00
@andrewseguin andrewseguin added target: patch This PR is targeted for the next patch release action: merge The PR is ready for merge by the caretaker labels Jun 6, 2024
@andrewseguin andrewseguin merged commit 6cf7f54 into angular:main Jun 6, 2024
28 checks passed
andrewseguin added a commit that referenced this pull request Jun 6, 2024
@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 Jul 7, 2024
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 area: build & ci Related the build and CI infrastructure of the project 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