Skip to content

build: account for rename of angular/code-of-conduct default branch #25199

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
Jun 30, 2022

Conversation

devversion
Copy link
Member

We just renamed the Angular code of conduct repository default branch
to main. This repository was not part of the large migration and is
now handled separately as a little clean-up.

We just renamed the Angular code of conduct repository default branch
to `main`. This repository was not part of the large migration and is
now handled separately as a little clean-up.
@devversion devversion added action: merge The PR is ready for merge by the caretaker merge safe target: patch This PR is targeted for the next patch release labels Jun 30, 2022
@devversion devversion requested a review from crisbeto June 30, 2022 12:53
@devversion devversion requested a review from a team as a code owner June 30, 2022 12:53
@devversion devversion merged commit e40ab27 into angular:main Jun 30, 2022
devversion added a commit that referenced this pull request Jun 30, 2022
…25199)

We just renamed the Angular code of conduct repository default branch
to `main`. This repository was not part of the large migration and is
now handled separately as a little clean-up.

(cherry picked from commit e40ab27)
devversion added a commit that referenced this pull request Jun 30, 2022
…25199)

We just renamed the Angular code of conduct repository default branch
to `main`. This repository was not part of the large migration and is
now handled separately as a little clean-up.

(cherry picked from commit e40ab27)
@devversion devversion assigned devversion and unassigned devversion Jul 1, 2022
@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 Aug 1, 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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants