Skip to content

build: preparation for primary branch rename in the Angular repos #24783

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 15, 2022
Merged

build: preparation for primary branch rename in the Angular repos #24783

merged 1 commit into from
Apr 15, 2022

Conversation

devversion
Copy link
Member

@devversion devversion commented Apr 15, 2022 •
edited
Loading

Preparation for the components repo as outlined our planning
document.

TODO once merged:

  • Cherry-pick into active v12 and v12 LTS branches

@devversion
build: preparation for primary branch rename in the Angular repos
abc2f69 
Preparation for the components repo as outlined our planning
document.
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Apr 15, 2022
@devversion devversion requested a review from a team as a code owner April 15, 2022 12:56
josephperrott
josephperrott approved these changes Apr 15, 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

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Apr 15, 2022
@zarend zarend merged commit bd5c094 into angular:master Apr 15, 2022
zarend pushed a commit that referenced this pull request Apr 15, 2022
@devversion @zarend
build: preparation for primary branch rename in the Angular repos (#2…
46657d0 
…4783)

Preparation for the components repo as outlined our planning
document.

(cherry picked from commit bd5c094)
@sync-by-unito sync-by-unito bot mentioned this pull request Apr 22, 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 20, 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.
3 participants
@devversion @josephperrott @zarend