Rename master to main branch
#60
Assignees
Comments
|
Pas de problème pour moi ! |
|
Sounds good to me! |
|
Done. |
Zeitsperre
added a commit
that referenced
this issue
Feb 16, 2024
### What kind of change does this PR introduce? * Deactivates the GitHub-Pages deployment * Constrains the temporal range of many of the notebooks examples in order to not overload memory limitations on ReadTheDocs ### Does this PR introduce a breaking change? Yes. Docs will now be served via [ReadTheDocs](https://docs.readthedocs.io/en/stable/) ### Other information: This PR is just waiting on #60
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Generic Issue
The new convention for GitHub repositories is to move from
mastertomain(https://www.techrepublic.com/article/github-to-replace-master-with-main-starting-in-october-what-developers-need-to-know/). The cookiecutter workflows expect amainbranch as well.There hasn't been much action going on here, so given that fact, I propose that once the Dependabot Pull Requests have been merged, we rename the trunk to
main.@RondeauG @sebastienlanglois any opposition?
The text was updated successfully, but these errors were encountered: