Propagating branch naming conventions

[Douglas Tan]

I'm in the midst of setting up repositories managed by gitosis to work
with gitflow. I'm wondering how I can make sure that all clones and/or
pulls of the repository use the same branch naming conventions. A
coworker suggested running "git flow init" on the .git repositories on
the gitosis server but that doesn't appear to be viable as I receive
errors "error: invalid option: --ignore-submodules".

Do I just need to change .git/config in the affected repository in
order to propagate the defaults to everyone?

[Vincent Driessen]

Hi Douglas,

> I'm wondering how I can make sure that all clones and/or
> pulls of the repository use the same branch naming conventions.

Since git-flow currently keeps the settings on a per-repo basis, there is
no good technical way to assure all users use the same branch naming
convention. Vanilla Git does not allow you to propagate settings from one
repo to another, so I guess you are stuck and have to deal with this
manually until git-flow supports this.

I've been discussing this already a bit with Vlad Dumitrescu, see this
thread: http://groups.google.com/group/gitflow-users/browse_thread/thread/9920a7df3d1c4908

> A coworker suggested running "git flow init" on the .git repositories
> on the gitosis server but that doesn't appear to be viable as I receive
> errors "error: invalid option: --ignore-submodules".

I think this error is related to you using an old Git version, can that
be the case?

Cheers,
Vincent

[Douglas Tan]

I figure I'll just have everyone use .gitconfig to "enforce" the
naming conventions. I'll keep an eye on that discussion then.

On Sep 7, 5:24 pm, Vincent Driessen <vinc...@datafox.nl> wrote:
> Hi Douglas,
>
> > I'm wondering how I can make sure that all clones and/or
> > pulls of the repository use the same branch naming conventions.
>
> Since git-flow currently keeps the settings on a per-repo basis, there is
> no good technical way to assure all users use the same branch naming
> convention. Vanilla Git does not allow you to propagate settings from one
> repo to another, so I guess you are stuck and have to deal with this
> manually until git-flow supports this.
>
> I've been discussing this already a bit with Vlad Dumitrescu, see this

> thread:http://groups.google.com/group/gitflow-users/browse_thread/thread/992...