-
Notifications
You must be signed in to change notification settings - Fork 13
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
Organizational changes to this repo's layout #119
Comments
github-actions
bot
added
the
Status: Needs Triage
This item is up for investigation.
label
Sep 5, 2024
Yes, this is an excellent strategy. |
This was referenced Sep 5, 2024
Done, although the HEAD of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upon internal discussions and following quite a lot of confusion and out-of-sync information, these repos:
Will undergo a re-organization of the repo layout:
release
branch will be introduced, of whichHEAD
will always point to the respectively latest release tag. This means that the content of therelease
branch will always be in sync with the latest release, the content of the zenodo record, and the respective DOIrelease
branch will be the default branch on GitHubdev
branch will be created, which is where ALL PRs other than releases must be targeted to.release
branch will be protected from direct pushes, and only accept PRs from thedev
branchThe text was updated successfully, but these errors were encountered: