Skip to content

build: changes for renaming primary branch to main #24828

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
Apr 28, 2022
Merged

build: changes for renaming primary branch to main #24828

merged 1 commit into from
Apr 28, 2022

Conversation

@devversion
Copy link
Member

Changes of the DIRECT phase for the "renaming master to
main" migration/planning doc.

@devversion
build: changes for renaming primary branch to main
8715794 
Changes of the `DIRECT` phase for the "renaming master to
main" migration/planning doc.
@devversion devversion added the target: patch This PR is targeted for the next patch release label Apr 25, 2022
@devversion devversion marked this pull request as ready for review April 25, 2022 13:02
@devversion devversion requested a review from a team as a code owner April 25, 2022 13:02
josephperrott
josephperrott approved these changes Apr 28, 2022
View reviewed changes
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

@josephperrott josephperrott added action: merge The PR is ready for merge by the caretaker merge safe labels Apr 28, 2022
@josephperrott josephperrott merged commit 090d40f into angular:main Apr 28, 2022
josephperrott pushed a commit that referenced this pull request Apr 28, 2022
@devversion @josephperrott
build: changes for renaming primary branch to main (#24828)
2968213 
Changes of the `DIRECT` phase for the "renaming master to
main" migration/planning doc.

(cherry picked from commit 090d40f)
@sync-by-unito sync-by-unito bot mentioned this pull request May 10, 2022
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 May 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@josephperrott josephperrott josephperrott approved these changes

Assignees

No one assigned

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@devversion @josephperrott