Skip to content

Switch from 'master' to 'main' branch #1417

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

Closed
kripken opened this issue May 10, 2021 · 28 comments
Closed

Switch from 'master' to 'main' branch #1417

kripken opened this issue May 10, 2021 · 28 comments

Comments

@kripken
Copy link
Member

kripken commented May 10, 2021

Most of the other WebAssembly/ repos have done this already.

Any concerns? I can't think of any CI or other factors that could be broken by this, but maybe I'm missing something.

@fgmccabe
Copy link

Sure.

@dtig
Copy link
Member

dtig commented May 11, 2021

No concerns, though taking a quick look through the repositories there are quite a few repositories that still use master as the default branch. Perhaps we can use this issue for tracking?

All the new repositories use main as the default branch, but the older repositories will need to be renamed. The only thing that would be affected is folks may run into local repos being out of date after the rename, but that should be fairly straightforward to fix.

@rossberg
Copy link
Member

Pardon my ignorance, but what is the context of this renaming, and why is it needed? (AFAICT, all the GH repos I've been contributing to use master.)

@fgmccabe
Copy link

If I Understand Correctly, this is part of Diversity, Equity and Inclusion. Admittedly, it is a very small part; but none-the-less a positive part.

@dtig
Copy link
Member

dtig commented May 11, 2021

The context here is to make the default naming conventions inclusive, see here for more detailed reading material, and supporting research. Github does this by default already(examples can be found in the newer proposals repositories), and has made the process of renaming quite seamless.

@rossberg
Copy link
Member

I see, thanks!

@kripken
Copy link
Member Author

kripken commented May 13, 2021

Ok, sounds like there are no objections. Making this change requires one of the repo owners to go to Settings->Branches->Default Branch and click the "Rename branch" icon (a pen). (edit: I had this wrong before)

I'm not sure who is a repo owner here, but perhaps @dschuff or @dtig ?

@dtig
Copy link
Member

dtig commented May 18, 2021

The design repository has now been renamed, this re-targets any open PRs, but does not update local environments. Any local branches will have to be updated to pull from the main branch.

To switch to using main in an existing local checkout -

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

Update existing branches to use main as the parent branch -

  • git branch -u origin/main <branch>

I'm keeping this issue open for tracking as we rename other repositories.

@kripken
Copy link
Member Author

kripken commented May 18, 2021

Thanks @dtig !

@dtig
Copy link
Member

dtig commented Sep 17, 2021

The default branch for several proposal repositories has been changed to main. There are some proposals that haven't been renamed yet as they are under active development, cc'ing the champions of the proposals to rename the branches in the way they find least disruptive. Happy to help too, so feel free to reach out if there are any questions or concerns.

cc: @rossberg, @aardappel, @aheejin, @conrad-watt, @yuri91, @lukewagner, @penzn, @fgmccabe

@yuri91
Copy link

yuri91 commented Sep 20, 2021

I just switched branch hinting from master to main.
Hopefully I didn't mess anything up.

@aheejin
Copy link
Member

aheejin commented Sep 20, 2021

exception handling repo's default branch has been switched to main too.

@conrad-watt
Copy link
Contributor

I don't appear to have permission to do this in the threads repo, possibly because I took over championship after the repo was created.

@dtig
Copy link
Member

dtig commented Sep 20, 2021

Thanks @aheejin and @yuri91. @conrad-watt Sorry about the permissions issue, should be fixed now.

@conrad-watt
Copy link
Contributor

done!

@aardappel
Copy link

Created a new main branch for Memory64, but I too don't have the privileges to change the default branch in the GitHub settings.

Following instructions from https://stevenmortimer.com/5-steps-to-change-github-default-branch-from-master-to-main/

@penzn
Copy link

penzn commented Sep 20, 2021

I've changed the default in flexible-vectors, but not deleting master yet, since there are important pull requests still open against it.

@dtig
Copy link
Member

dtig commented Sep 20, 2021

@aardappel Permissions should be fixed now. The official instructions on how to rename are here. @penzn This also automatically updates open PRs, the only thing this would not update are local environments, so if you have existing branches with state in them, but there's probably local state associated with the PRs, so it makes sense to keep the master branch around as needed.

@aardappel
Copy link

@dtig thanks, all done. master deleted.

@penzn
Copy link

penzn commented Sep 20, 2021

there's probably local state associated with the PRs, so it makes sense to keep the master branch around as needed.

Looks like the diff is still tied to the branch it was made against originally: WebAssembly/flexible-vectors#27. Maybe Github would clean this up eventually, but a any rate we will repoint the change before merging.

@lukewagner
Copy link
Member

done!

sunfishcode added a commit to sunfishcode/spec that referenced this issue Oct 13, 2021
…ain".

Several WebAssembly organization repositories have changed their default
branch from "master" to "main": see WebAssembly/design#1417 for details.
This PR updates URLs in the spec repository to point to "main" instead of
"master", for repositories which have done so.
sunfishcode added a commit to WebAssembly/spec that referenced this issue Oct 14, 2021
…ain".

Several WebAssembly organization repositories have changed their default
branch from "master" to "main": see WebAssembly/design#1417 for details.
This PR updates URLs in the spec repository to point to "main" instead of
"master", for repositories which have done so.
fgmccabe pushed a commit to WebAssembly/js-promise-integration that referenced this issue Apr 20, 2022
…ain".

Several WebAssembly organization repositories have changed their default
branch from "master" to "main": see WebAssembly/design#1417 for details.
This PR updates URLs in the spec repository to point to "main" instead of
"master", for repositories which have done so.
@fidanticaret
Copy link

Most of the other WebAssembly/ repos have done this already.

Any concerns? I can't think of any CI or other factors that could be broken by this, but maybe I'm missing something.

@sunfishcode
Copy link
Member

sunfishcode commented Aug 22, 2022

@penzn
Copy link

penzn commented Aug 22, 2022

Are we going to switch branches in archived repositories? 😉 A good portion of those are, for exmple bulk-memory-operations, lld, and multi-value.

@sunfishcode
Copy link
Member

I've now separated the list into Not Archived and Archived.

@dtig
Copy link
Member

dtig commented Aug 22, 2022

Repositories are merged and archived, so those weren't updated:

Repositories that are for inactive proposals, or parts of proposals that are merged are now archived:

Recent repositories that defaulted to Organization defaults (which are now updated to use main as well):

For repositories that have been inactive for the past year, I've updated them to default to main:

Repositories that have seen activity recently and were not updated:

For the repositories in the last section, please reach out if there are any concerns with updating them, if not I'll update the repos end of this week.

@sunfishcode
Copy link
Member

@dtig Friendly ping ;-). If we can rename master to main in these last two repos, we can close out this issue :-).

@dtig
Copy link
Member

dtig commented Nov 4, 2022

Thanks for the ping, renamed the last two repositories. I'm closing this issue for now, please reopen if I've missed something!

@dtig dtig closed this as completed Nov 4, 2022
raoxiaojia pushed a commit to WasmCert/spec that referenced this issue Apr 29, 2025
…ain".

Several WebAssembly organization repositories have changed their default
branch from "master" to "main": see WebAssembly/design#1417 for details.
This PR updates URLs in the spec repository to point to "main" instead of
"master", for repositories which have done so.
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