Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Persisting git flow init settings #95

julian7 opened this Issue · 6 comments

6 participants


I think setting up git flow for multiple developers can be very tedious and error-prone (if we don't use default settings). Therefore it would be great to have a file in top level directory (let's call it .gitflow for now), which stores all the answers a git flow init might require.

Then, when a new developer joins, he/she would be able to run 'git flow init' with no arguments, and no questions whatsoever.

Besides, you can achieve the same functionality with the following two commands:

Saving data:
git config --get-regexp '^gitflow' | sed "s/ /' '/" | while read A; do echo "git config --local '$A'"; done > git rev-parse --show-toplevel/.gitflow

Instead of git flow init:
. ./.gitflow


I'd like to find a solution for this problem. There has already been some discussion on the topic, I may say. To read up on it, please see


You can have alteast half of the questions answered for you by having a file called .gitconfig in your home directory, and including this:

[gitflow "prefix"]
  feature = feature/
  release = release/
  hotfix = hotfix/
  support = support/
  versiontag = v

Of course, change yours where appropriate. Unfortunately the scripts will still ask for "master" and "develop" branches.


I think the idea I brought up works better, because it creates a file which can be put into version control. Therefore all the settings can be reproduced on setting up a new development environment.

So far I'm fine with this solution, nevertheless it would be great to have it documented somewhere :)


Second for pushing to version control. Looking to use git flow on multiple projects with multiple conventions, so ~/.gitconfig doesn't work for how I use it.


.gitflow configuration file could be put in a "central" bare repository (by default origin)


Here's a pull request that could address this issue: nvie/gitflow#147

I'd be happy to get some feedback on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.