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

fix(dev-infra): detect multiple target labels as invalid #40156

Closed

Conversation

josephperrott
Copy link
Member

When multiple target labels are applied to a PR, it should be considered
invalid as our tooling does not support a single PR targetting multiple
trains/versions.

When multiple target labels are applied to a PR, it should be considered
invalid as our tooling does not support a single PR targetting multiple
trains/versions.
@josephperrott josephperrott added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) labels Dec 16, 2020
@ngbot ngbot bot modified the milestone: Backlog Dec 16, 2020
@google-cla google-cla bot added the cla: yes label Dec 16, 2020
Copy link
Member

@gkalpak gkalpak left a comment

Choose a reason for hiding this comment

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

our tooling does not support a single PR targetting multiple trains/versions

I think this part of the commit sounds a little confusing. We do support merging into multiple trains/versions. For example, the target: patch label could result in merging into master, RC and patch. The commit message could be a little more clear on what the tooling does not support (multiple target labels?).

Otherwise lgtm 👍

Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM. One minor nit.

dev-infra/pr/merge/target-label.ts Show resolved Hide resolved
@josephperrott josephperrott marked this pull request as ready for review January 7, 2021 18:29
dev-infra/pr/merge/pull-request.ts Show resolved Hide resolved
dev-infra/pr/merge/target-label.ts Outdated Show resolved Hide resolved
Copy link
Member

@gkalpak gkalpak left a comment

Choose a reason for hiding this comment

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

LGTM (as soon as CI is happy) 🚀

@josephperrott josephperrott added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 8, 2021
atscott pushed a commit that referenced this pull request Jan 11, 2021
When multiple target labels are applied to a PR, it should be considered
invalid as our tooling does not support a single PR targetting multiple
trains/versions.

PR Close #40156
@atscott atscott closed this in 3d7e207 Jan 11, 2021
@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 Feb 11, 2021
@josephperrott josephperrott deleted the multiple-target-error branch August 31, 2023 17:33
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: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) cla: yes 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

3 participants