nvie / gitflow

Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
http://nvie.com/posts/a-successful-git-branching-model/
Other
26.6k stars 2.66k forks source link

Git flow configuration #6448

Open Narven opened 4 years ago

Narven commented 4 years ago

Is there any gitflow configuration file that can be shared, so that gitflow works the same way across all developers in a team.

There are several "ways" that gitflow works, that are against how you should work in a team.

Example:

Is there any way to configure this by default?

Thanks

reshadf commented 4 years ago

This is not something for Git flow to take care of. You should set this up in your Gitlab/Github and block direct pushing to develop.

m4l490n commented 4 years ago

Agree with @reshadf, that is more related to your workflow or your branching scheme. Also, a PR usually happens "before" the developer finishes the feature, so they can finish a peer-reviewed feature.

Finishing a feature SHALL definitely merge back to develop, that's one of the purposes of gitflow, otherwise, you will end up with endless branches and you have to merge those features into develop anyways, unless you want to create branches from branches and merge one feature with another, etc.