Skip to content

Handle pre-release channels #90

@taorepoara

Description

@taorepoara

Is your feature request related to a problem? Please describe.
I can't properly create the beta versions of my project.

Describe the solution you'd like
Manage pre-release depending on the current branch and a list of the pre-release branches in a config file.

Describe alternatives you've considered
Instead of getting the pre-release channel (for example beta) with the config and the current branch, the user could give the channel in the version sub-command.

Additional context
Here is how semantic-release handle it: https://github.com/semantic-release/semantic-release/blob/cd6136d67ee83b262a34dd7a230e1e3ae4799ed0/docs/usage/workflow-configuration.md#pre-release-branches

The advantage of this tool over semantic-release (in my opinion) is that you just calculate the next version and change-log file when semantic-release goes to far.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions