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

Rename "master" branch to "main" #244

Closed
dims opened this issue Jun 2, 2021 · 5 comments
Closed

Rename "master" branch to "main" #244

dims opened this issue Jun 2, 2021 · 5 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. wg/naming Categorizes an issue or PR as relevant to WG Naming.

Comments

@dims
Copy link
Member

dims commented Jun 2, 2021

Steps and check list are here:
https://www.kubernetes.dev/resources/rename/

@dims
Copy link
Member Author

dims commented Jun 2, 2021

/assign @kubernetes/owners

@spiffxp
Copy link
Member

spiffxp commented Jun 2, 2021

/wg naming
umbrella issue ref: kubernetes/org#2222

For future reference it would be helpful if you can confirm you've walked through the checklist. Noting for @kubernetes/owners that the instructions as posted at kubernetes.dev are not easily copy-pasteable into an issue body as a checklist.

That said, I took a quick grep through kubernetes/klog and kubernetes/test-infra, and can't see that you'll have any pre/post migration changes to make. So +1 as a member of @kubernetes/owners

Things I would suggest adding to the body:

- [x]  Once all non-disruptive tasks have been completed and disruptive tasks have been identified, assign the GitHub Management team (@kubernetes/owners) for approval.
- [x] Once the issue has been approved, send a notice to your SIG’s mailing list about the potential branch rename.
- [x] Rename the default branch from master to main using the GitHub UI by following the official instructions.
- [x] Trial the local development experience with a pre-rename clone.
- [x] Send a notice about the branch rename to your SIG’s mailing list. Include the link to the GitHub instructions to rename your local branch.

@k8s-ci-robot k8s-ci-robot added the wg/naming Categorizes an issue or PR as relevant to WG Naming. label Jun 2, 2021
@dims
Copy link
Member Author

dims commented Jun 2, 2021

Note to sig-instrumentation mailing list - https://groups.google.com/g/kubernetes-sig-instrumentation/c/GmdVotAvZTw/m/wgpOM35mAgAJ

@spiffxp
Copy link
Member

spiffxp commented Jun 2, 2021

/sig instrumentation
/priority important-soon
/kind cleanup

@k8s-ci-robot k8s-ci-robot added sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Jun 2, 2021
@dims
Copy link
Member Author

dims commented Jun 3, 2021

Done!

@dims dims closed this as completed Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. wg/naming Categorizes an issue or PR as relevant to WG Naming.
Projects
None yet
Development

No branches or pull requests

3 participants