Skip to content

release: handle multiple branches #31

Open
@kousu

Description

@kousu

Update the actions workflows, both sync-upstream.yml and release.yml, so that we can maintain an arbitrary number of feature branches, starting with:

These should all be regularly rebased on upstream/main, and, except for release-action itself, built and pushed to /releases when a new upstream release comes out.

Also, make sure to handle

which should be the merge of both of those (so, probably, cornerstone rebased on git-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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions