Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to configure the naming convention for git-flow branches #250

Open
novopl opened this issue Nov 19, 2019 · 0 comments
Open

Ability to configure the naming convention for git-flow branches #250

novopl opened this issue Nov 19, 2019 · 0 comments
Assignees
Labels
Projects
Milestone

Comments

@novopl
Copy link
Owner

novopl commented Nov 19, 2019

What?

Add the ability to configure how the feature, hotfix and task branches are named. So that peltak can be used with different flows.

Why?

This would make it possible to use peltak with different flows than git-flow. For trunk based development you won't always use the feature/* prefix as all branches are feature branches.
Currently if you try to run the peltak feature merged in a setup like that it will exit with error saying you are not on a feature branch. This should be configurable so the peltak can be used in a wider range of projects.

How?

<Optional - How this should be implemented, should be technical>

@novopl novopl self-assigned this Nov 19, 2019
@novopl novopl added the feature label Nov 19, 2019
@novopl novopl added this to Capture in 1.0 via automation Nov 19, 2019
@novopl novopl added this to the 1.0 milestone Nov 19, 2019
@novopl novopl moved this from Capture to Should in 1.0 Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
1.0
  
Should
Development

No branches or pull requests

1 participant