Skip to content
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

🛠 Repo: Rename master branch to main #5051

Closed
5 tasks done
JoshuaKGoldberg opened this issue Dec 27, 2023 · 2 comments · Fixed by #5130
Closed
5 tasks done

🛠 Repo: Rename master branch to main #5051

JoshuaKGoldberg opened this issue Dec 27, 2023 · 2 comments · Fixed by #5130
Assignees
Labels
area: repository tooling concerning ease of contribution status: accepting prs Mocha can use your help with this one! type: chore generally involving deps, tooling, configuration, etc.

Comments

@JoshuaKGoldberg
Copy link
Member

Tooling Suggestion Checklist

Overview

Per https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main, the default branch for repositories is now main. We're going to apply the same change to this repo and its tooling. Filing this issue for tracking.

Additional Info

https://github.com/github/renaming has more details on the context and practices around the rename.

This'll need a find-and-replace in any docs, workflows, etc. that refer to branches/Git/etc.

Intentional follow-up to #5038.

@JoshuaKGoldberg JoshuaKGoldberg added status: accepting prs Mocha can use your help with this one! type: chore generally involving deps, tooling, configuration, etc. area: repository tooling concerning ease of contribution labels Dec 27, 2023
@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Dec 27, 2023
@JoshuaKGoldberg JoshuaKGoldberg added status: blocked Waiting for something else to be resolved and removed status: accepting prs Mocha can use your help with this one! labels Dec 27, 2023
@JoshuaKGoldberg
Copy link
Member Author

We'll do this, but need to wait until we have website access and are a bit more experienced as maintainers. Likely to wait until at least one release from master is done.

@JoshuaKGoldberg JoshuaKGoldberg added status: in triage a maintainer should (re-)triage (review) this issue and removed status: in triage a maintainer should (re-)triage (review) this issue labels Feb 9, 2024
@JoshuaKGoldberg
Copy link
Member Author

We have website access now (mostly), and shoutout to @voxpelli for running the v10.4.0 release. Marking as unblocked!

@JoshuaKGoldberg JoshuaKGoldberg added status: accepting prs Mocha can use your help with this one! and removed status: blocked Waiting for something else to be resolved labels Mar 27, 2024
@JoshuaKGoldberg JoshuaKGoldberg moved this from Backlog to Up Next in Maintenance Reboot Mar 27, 2024
@JoshuaKGoldberg JoshuaKGoldberg moved this from Up Next to In Progress in Maintenance Reboot Mar 27, 2024
@JoshuaKGoldberg JoshuaKGoldberg moved this to In Progress in Maintenance Reboot Mar 27, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Maintenance Reboot Jun 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: repository tooling concerning ease of contribution status: accepting prs Mocha can use your help with this one! type: chore generally involving deps, tooling, configuration, etc.
Projects
Development

Successfully merging a pull request may close this issue.

1 participant