Skip to content

update release actions to support GitFlow branching model #42

@kelly-sovacool

Description

@kelly-sovacool

Currently, the draft-release and post-release actions assume a GitHub Flow branching model with the main branch serving as the dev branch. However, we sometimes use the GitFlow model where there are separate dev and main branches such as for CCBR/Dockers2.

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