joseph.e...@gmail.com
unread,Apr 10, 2013, 11:06:33 AM4/10/13Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to gitflo...@googlegroups.com
Hi all, I've used git-flow on and off since it was first released but at my current dayjob I am not currently using it. Some of the developers aren't really version control experts which has led to some near-disasters. I want to bring git-flow in here but I am not sure if it will work with our model via configuration, if I will have to fork it and make some changes, or worse comes to worst write my own small git add on. Let me explain how things work here:
1. New topic branch is created off of master, either named hotfix/ticket_XXXX or feature/ticket_XXXX. The only matter that the topic branch prefixes have is that jenkins is looking for either of those prefixes for CI/deployment to the 'testing' environment.
2. Aforementioned topic branch is pushed to GitHub, which sends a post-receive hook to our jenkins server. Jenkins then merges any new commits in branches with hotfix/* or feature/* into the testing branch, and deploys this branch via capistrano to the testing environment.
3. Once things appear good, the developer is to squash merge their topic into master, then delete both their local and remote topic branches.
So basically, it is sort of similar to git-flow but there is no dual main branch (master and develop) due to the CI stuff. I tried to test out git-flow by specifying master in both the 'next release' and production branches, but it failed to initialize.
Thoughts?