Thanks for posting this, I'm always interested in how to advise our users better so feel free to ask questions or disagree. BTW We're trying to keep <a href="http://doc.gitlab.com/ee/workflow/gitlab_flow.html" rel="nofollow">http://doc.gitlab.com/ee/workflow/gitlab_flow.html</a> updated with the latest learnings although it is very similar to the blog post.
Everybody is talking about GitLab these days but actually I am interested to see number of those who are ready to migrate to it for real... It still a lot of talk and little realization...
I still haven't seen a better git branching model than <a href="https://gist.github.com/17twenty/6733076" rel="nofollow">https://gist.github.com/17twenty/6733076</a> (aka feature branching model). I've found this model works well for smaller apps and can scale easily with modularization and feature flags.
Yup, that's usually what I prefer to do myself anyway.<p>Working on teams we usually commit to '$username/$feature' branches though, to keep it reasonably clean and not potentially pollute others' namespaces. We're also not allowed to merge in our own PRs (usually, unless it's tiny) to force code reviews, which generally works out quite nicely.