Hi Erwin,
Finding the right branching/deployment model in Git is pretty much up to
your imagination :)
However, if you're not the creative type, there's a de-facto best practice
model here: http://nvie.com/posts/a-successful-git-branching-model/
Maybe you'll find this model inspiring. Note
Oh, by the way, the model is commonly known as git-flow, and there's a
mailing list dedicated to it:
https://groups.google.com/forum/#!forum/gitflow-users
And also a git-wrapper that makes it easier to use (but don't start using it
before you know what's going on under the hood):
Thanks Thomas .. I found it yesterday ... but good to know that's
you're backing it ... excellent article
I learn a lot and started our model base on it
On Jul 17, 10:16 pm, Thomas Ferris Nicolaisen tfn...@gmail.com
wrote:
Oh, by the way, the model is commonly known as git-flow, and there's a
I guess it's a stupid process ... resolved to change it to simple
'master' and 'develop' branches from which I deploy to the remote
server , whi did I try to make it complex...
On Jul 16, 8:50 am, erwin kadou...@gmail.com wrote:
I don't know if the way I set my deployment is the cause , but I