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

Renaming the default branch (master) to main #29

Closed
3 tasks
GrooveCS opened this issue Apr 16, 2021 · 5 comments
Closed
3 tasks

Renaming the default branch (master) to main #29

GrooveCS opened this issue Apr 16, 2021 · 5 comments
Assignees

Comments

@GrooveCS
Copy link

Renaming the default branch (master) to main in the repo.
GitHub's new practice of main as the default repo name. Learn more.

Checklist

  • Documentation update
  • Updating the guides (wiki, .md files, etc.)
  • Communicating it (Slack)
@RinkiyaKeDad
Copy link
Member

I was also thinking of doing this, thanks for opening the issue @GrooveCS!

@RinkiyaKeDad RinkiyaKeDad self-assigned this Apr 17, 2021
@RinkiyaKeDad
Copy link
Member

Made the change. If anyone wants to fix their local clone:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

cc @alenkacz @navidshaikh

@navidshaikh
Copy link
Member

AFAIK, master --> main branch transition is not happening for any other k8s/k8s-sig repos. I think it will be a coordinated effort across repos to change and update docs/CI jobs etc.
@nikhita is it fine to change default branch individually per repo or it should wait ?

@nikhita
Copy link
Member

nikhita commented Apr 25, 2021

@nikhita is it fine to change default branch individually per repo or it should wait ?

It is fine to change the default branch individually. https://k8s.dev/rename has more details if you'd like to do it for this repo.

@RinkiyaKeDad
Copy link
Member

Umm so I had already changed the branch name before Navid commented. I took a look at the link Nikhita mentioned and seems like the only step missing/applicable was dropping a mail to the SIG-Architecture mailing list. Have done that now.

Closing this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants