-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No push on finish #2
Comments
Hello @virus2016, Production branch is protected and you are only available to push the commits based on the origin/production. The only case where you are not able to push on origin/production, is the case when your local branch production is synchronized with origin/production. |
We have a private repo. The structure is: Master (protected) We usually PR into develop from branches created then develop into master. Do you think we should do it another way? |
The develop branch shouldn't be protected because, gflow tools try to reset develop (if syncAfterFinish is true). |
Our develop branch must be in a working state so that a developer can run the project and base features from there which is why it is protected. |
It would be brilliant if the finish command has an option not to merge to master and push. |
Ok in your case, just change the configuration by this: {
"production": "develop",
"develop": "develop"
} It avoid the merge on your production (master). |
Hi @Romakita,
Are we able not to push the production on finish as we have protected branches?
Thanks!
The text was updated successfully, but these errors were encountered: