Make configuratin options agnostic to branch naming #228

Open
baby-gnu opened this Issue Jul 4, 2012 · 0 comments

Comments

Projects
None yet
1 participant

baby-gnu commented Jul 4, 2012

Is there chance that the "production-ready state" branch be named something like "prod" instead of "master" which is not that meanful and can be confusing for new comers?

My config looks like the following:

gitflow.branch.master=prod
gitflow.branch.develop=master

The default configuration would became:

gitflow.branch.prod=master
gitflow.branch.develop=develop

Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment