Closed kMutagene closed 4 weeks ago
Yes, this is an excellent strategy.
Done, although the HEAD of release
will point to to the latest tag after the next release. I have done it this way so that contribution rules are visible on the default branch from now on.
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
branch