Skip to content

build: cleanup remaining references to master branch #24866

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
May 4, 2022

Conversation

devversion
Copy link
Member

We should clean up all references to master and use main
where possible.

We should clean up all references to `master` and use `main`
where possible.
@devversion devversion requested a review from crisbeto May 3, 2022 13:26
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels May 3, 2022
@devversion devversion marked this pull request as ready for review May 3, 2022 13:26
@devversion devversion requested review from a team, jelbourn, mmalerba and andrewseguin as code owners May 3, 2022 13:26
Copy link
Member

@crisbeto crisbeto 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 action: merge The PR is ready for merge by the caretaker and removed merge safe labels May 3, 2022
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 target: major This PR is targeted for the next major release and removed target: patch This PR is targeted for the next patch release labels May 4, 2022
@devversion devversion merged commit f2bcf50 into angular:main May 4, 2022
@devversion devversion deleted the cleanup-main-rename branch May 4, 2022 11:47
@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 Jun 4, 2022
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 target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants