git flow init

841 views
Skip to first unread message

pro-...@optusnet.com.au

unread,
Dec 24, 2011, 10:06:08 PM12/24/11
to gitflo...@googlegroups.com
Hi,

I've recently started using git flow on windows, and I have to say, I like it very much. Great work.

One thing that I don't understand is why everybody who uses the same repo has to run the git flow init command?

Would it not be better to have a .gitflow file in the root of the directory? Much like .gitignore, .gitattributes and .gitmodules?

Aseem Kishore

unread,
Dec 24, 2011, 10:34:34 PM12/24/11
to gitflo...@googlegroups.com
Great idea! +1

Aseem

Mark Derricutt

unread,
Dec 24, 2011, 11:51:07 PM12/24/11
to gitflo...@googlegroups.com

One problem against this is that configuration is sometimes user specific ( I occasionally switch to an alternate development branch for epic like streams, which I really should write as a gitflow command), I wouldnt really want that pushed upstream.

-- Sent from an Android

Peter van der Does

unread,
Dec 25, 2011, 12:02:30 PM12/25/11
to gitflow-users
I thought of the same idea last night after I wrote a feature to
implement hooks. I just created an issue on github:
https://github.com/nvie/gitflow/issues/183

I shall be working on this.

On Dec 24, 11:51 pm, Mark Derricutt <m...@talios.com> wrote:
> One problem against this is that configuration is sometimes user specific (
> I occasionally switch to an alternate development branch for epic like
> streams, which I really should write as a gitflow command), I wouldnt
> really want that pushed upstream.
>
> -- Sent from an Android
> On Dec 25, 2011 4:34 PM, "Aseem Kishore" <aseem.kish...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Great idea! +1
>
> > Aseem
>

Mark Derricutt

unread,
Dec 25, 2011, 2:42:12 PM12/25/11
to gitflo...@googlegroups.com

Just a thought tho, you'll still need to run git flow unit on checkout anyway as a clone doesn't actually create local branches..

-- Sent from an Android

Peter van der Does

unread,
Dec 25, 2011, 3:40:27 PM12/25/11
to gitflow-users
You don't have to run git flow init if the gitflow settings are cloned
over as well.
The reason you currently have to run git flow init, is the fact that
the configuration of gitflow is stored in the .git/conf file. This
file isn't cloned on git clone. Any other directory is, so when you
clone a gitflow enabled repo and do for example git flow feature start
my-feature, the feature branch prefix is know and is also consistent
with the original repo.


On Dec 25, 2:42 pm, Mark Derricutt <m...@talios.com> wrote:
> Just a thought tho, you'll still need to run git flow unit on checkout
> anyway as a clone doesn't actually create local branches..
>
> -- Sent from an Android
> On Dec 26, 2011 6:02 AM, "Peter van der Does" <pvanderd...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages