forked from go-gitea/gitea
-
Notifications
You must be signed in to change notification settings - Fork 2
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
release: handle multiple branches #31
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update the actions workflows, both
sync-upstream.yml
andrelease.yml
, so that we can maintain an arbitrary number of feature branches, starting with:release-action
(release-action
#2)git-annex
(git-annex
#1)cornerstone
(cornerstone
: Display NIfTI and dicom image previews #30)These should all be regularly rebased on
upstream/main
, and, except forrelease-action
itself, built and pushed to /releases when a new upstream release comes out.Also, make sure to handle
git-annex-cornerstone
(cornerstone
+git-annex
#24)which should be the merge of both of those (so, probably,
cornerstone
rebased ongit-annex
)All of these steps should run as separate jobs so it's easy to see what went wrong when something goes wrong. The problem with the current workflows is they do everything in one shot, so it's difficult to scale and even more difficult to do #17.
The text was updated successfully, but these errors were encountered: