Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Gitflow is not designed to support pull requests, it's more of high trust process. I tend to call gitflow with PRs "gateflow," you'll need to manage it manually.
-
@SortOfTested Yeah, it's not well suited for PRs. Any idea how to manage hotfixes if we still want to keep the idea of a master and develop branch?
-
To provide a workaround, you may want to adopt a fork repo model. You can gitflow all the way to the fork trunk, and then PR from that fork trunk to the release repo, similar to how a private->public promotion models work.
-
@ScriptCoded
Sans my other suggestion, you'll need to make PRs non-mandatory, or migrate to gitlab which lets you modify the conventional gated flows. -
@SortOfTested I'll have a look at a forking model. We recently moved from BitBucket, so I don't think another move would be appreciated... :'(
Thanks for the advice :) -
@vorticalbox Yeah, but that defeats the purpose of the pr, since it would already be in master
Related Rants
Has anyone had success with GitFlow hotfixes and GitHub branch protection rules? Finishing a hotfix requires pushing directly to develop, but GitHub prevents it if PR policies are set up :/
question
github
pullrequest
gitflow
hotfix