neoskop / flow-bump Goto Github PK

Add an option to create a version from a specific commit hash

Get options keepBranch and tagBranch from cli args.

Include tags in git push/pull

Push Tags to origin

To propper support hotfixes/minor releases on legacy versions we need support-branches.

TODO:
remove flow-bump release
remove flow-bump hotfix
remove flow-bump fix
update flow-bump patch to create a hotfix/* branch
add flow-bump hotfix as alias to flow-bump patch
add option to flow-bump final to not merge into master, but a support/* branch and also not merge develop

Use tagBranch option from load function

Push the support branch, not master when finalize to Support Version.

Add scripts to YAML config, for example to build, publish etc.

A hotfix is for a legacy version and thereby it should be merged into current master/develop.
Instead, the fix should be sherrypicked onto develop.

--merge
no (default) dont merge
master merge into master
develop merge into develop
all merge into master and develop

Implies --tag-branch option

Add Init-Version Option to start a Release with a alpha/beta/rc version insteand of pre.

After resolving the merge conflicts and continuing you get the following error message:

Command failed: git commit --no-edit --no-ff
error: unknown option `no-ff'
usage: git commit [<options>] [--] <pathspec>...

TODO: remove the --no-ff option in the commit command after conflict resolving

Delete the remote branch as well, when the local release/hotfix branch is deleted

Add option to create and finalise version in one step

Use --no-ff option for release branch merging

Add commands to read and write config values for local and global configuration

Load the YAML config file from current directory, parent directories or home directory to support global settings.