No push on finish

[virus2016]

Hi @Romakita,

Are we able not to push the production on finish as we have protected branches?

Thanks!

[Romakita]

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.
On which repository you have the problem ?

[virus2016]

We have a private repo.

The structure is:

Master (protected)
Develop (protected)

We usually PR into develop from branches created then develop into master. Do you think we should do it another way?

[Romakita]

The develop branch shouldn't be protected because, gflow tools try to reset develop (if syncAfterFinish is true).

[virus2016]

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.

[virus2016]

It would be brilliant if the finish command has an option not to merge to master and push.

[Romakita]

Ok in your case, just change the configuration by this:

{
  "production": "develop",
  "develop": "develop"
}

It avoid the merge on your production (master).