You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
The text was updated successfully, but these errors were encountered:
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>
The text was updated successfully, but these errors were encountered: