Skip to content

Support "git flow" branches, optionally create PRs #22

@cball

Description

@cball

When using git flow, the branches are setup in the following way:

  • dev (alpha)
  • beta (beta)
  • release (master)

In this mode, the script currently tries to delete the local copy of master, which is not good.

This also brings up concern of protected branches. I see 3 scenarios:

  • ci does the commit, and ci is a protected user that is allowed to push to master & dev
  • push to an intermediate branch, open up browser to create a PR
  • require protected branches to be off

My concern with the PR flow is that if the PR is not immediately merged, the history will be wrong.

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