Skip to content

build: lay foundation for migrating to ng-dev release tooling #22167

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Mar 15, 2021
Merged

build: lay foundation for migrating to ng-dev release tooling #22167

merged 1 commit into from
Mar 15, 2021

Conversation

josephperrott
Copy link
Member

Configure the release tooling from ng-dev.

@josephperrott
build: lay foundation for migrating to ng-dev release tooling
7e284fd 
Configure the release tooling from ng-dev.
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 9, 2021
@josephperrott josephperrott added target: patch This PR is targeted for the next patch release area: build & ci Related the build and CI infrastructure of the project action: merge The PR is ready for merge by the caretaker merge safe labels Mar 9, 2021
@mmalerba mmalerba removed the action: merge The PR is ready for merge by the caretaker label Mar 10, 2021
@josephperrott josephperrott marked this pull request as ready for review March 11, 2021 17:35
@josephperrott josephperrott requested a review from a team as a code owner March 11, 2021 17:35
@josephperrott josephperrott added the action: merge The PR is ready for merge by the caretaker label Mar 11, 2021
@josephperrott josephperrott requested review from mmalerba and removed request for a team March 11, 2021 19:31
mmalerba
mmalerba approved these changes Mar 11, 2021
View reviewed changes
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

LGTM

Please note: the merge ready label should only be applied after the PR has been approved/LGTM'd

@mmalerba mmalerba merged commit d66cb83 into angular:master Mar 15, 2021
mmalerba pushed a commit that referenced this pull request Mar 15, 2021
@josephperrott @mmalerba
build: lay foundation for migrating to ng-dev release tooling (#22167)
97bad00 
Configure the release tooling from ng-dev.

(cherry picked from commit d66cb83)
@josephperrott josephperrott deleted the prep-release-tooling branch March 15, 2021 20:51
This was referenced Mar 17, 2021
Closed
Merged
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@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 Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@mmalerba mmalerba mmalerba approved these changes

Assignees

No one assigned

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@josephperrott @mmalerba