Mark Ferrell writes:
> push repository, but our use case relies on the pull branch being
> different than the push branch. It would seem that git would need a
> branch..push directive for this to work out.
I thought that you can tell recent versions of Git to pay attention
to the remote.*.push
I was trying to setup a git client to deal with our version of a
triangular workflow and found that there where no configuration
directives which supported our use case.
Developers create and commit to branches named dev//TOPIC
(Branch permissions are handled by Gitolite). If the topic is
prefixe
2 matches
Mail list logo
