search

MetabolicAtlas / standard-GEM

The standard for open-source GEMs on GitHub
https://www.biorxiv.org/content/10.1101/2023.03.21.512712
Creative Commons Attribution 4.0 International
19 stars 5 forks source link

rename _master_ to _main_ #6

Closed mihai-sysbio closed 3 years ago

mihai-sysbio commented 4 years ago

There is a discussion on the web to rename the master branch to main, for diversity reasons. Somebody from GitHub (was it the CEO?) said something about potentially a GitHub-wide implementation. I'm not sure if it's best to wait for that rather than to push for the switch immediately.

haowang-bioinfo commented 4 years ago

IMHO, immediately

Midnighter commented 4 years ago

We renamed the master branch on cobrapy to stable. I agree, the sooner you do it the less hassle for everyone.

Midnighter commented 4 years ago

Please note that you should also adjust the standard document description:

:red_square: Git branches The GEM repository must have at least two branches: master and develop.

mihai-sysbio commented 4 years ago

Thanks for the notice @Midnighter. As of the current version, it's still master. This change will be implemented for the next release, unless we find reasons not to.

draeger commented 4 years ago

Please note that GitHub officially says to wait for its new updates which will seamlessly provide support for changing master branch to main branch.

Guidelines by GitHub on renaming branch name: https://github.com/github/renaming. At the moment, renaming it can cause problems when using GitHub pages.

mihai-sysbio commented 4 years ago

I was not aware of that, thanks for sharing that link @draeger! Consequently, this issue is in the Backlog for now, to be dealt with after GitHub implements the changes. It sounds like a better idea to ask people to rename the branches only after that.

edkerk commented 3 years ago

Since January 2021, GitHub no longer advises to wait with changing master to main, so this can be implemented.

mihai-sysbio commented 3 years ago

This issue has been resolved via #32. Please open a new issue if any follow-up is required.