Skip to content

build: branch manager should use "7.3.x" as patch branch #15097

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
Feb 6, 2019

Conversation

devversion
Copy link
Member

Updates the branch manager to validate patch PRs against the 7.3.x branch. This is necessary because currently some PRs are marked as failing because they no longer apply to the outdated 7.2.x branch.

cc. @josephperrott should we somehow add this to the release instructions? or should the branch manager automatically pick up the proper branch somehow (e.g. by checking the "package.json")

Updates the branch manager to validate patch PRs against the
`7.3.x` branch. This is necessary because currently some PRs
are marked as failing because they no longer apply to the
outdated `7.2.x` branch.
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Feb 5, 2019
@devversion devversion requested a review from jelbourn as a code owner February 5, 2019 22:48
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 5, 2019
@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Feb 6, 2019
@josephperrott
Copy link
Member

Ideally, we would have it automated. I will have to think through about how to do that best.

@jelbourn jelbourn merged commit a3ab5e3 into master Feb 6, 2019
jelbourn pushed a commit that referenced this pull request Feb 11, 2019
Updates the branch manager to validate patch PRs against the
`7.3.x` branch. This is necessary because currently some PRs
are marked as failing because they no longer apply to the
outdated `7.2.x` branch.
@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 10, 2019
@devversion devversion deleted the build/branch-manager-7.3.x-patch-branch branch June 26, 2021 16:32
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 PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants