Giters

nvie / gitflow

Git extensions to provide high-level repository operations for Vincent Driessen's branching model.

Home Page:http://nvie.com/posts/a-successful-git-branching-model/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Git flow configuration

Narven opened this issue · comments

commented

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:

  • After you create a feature branch from develop and work on it... and you finish it... that should NEVER ALLOW that branch to be merged into develop locally and even more important... not on origin. That's why in the XXI century we have PR's.
  • Should never allow under any kind of circumstance the deletion of branches (mainly origin) deleting on local should always be false (unless specified differently)

Is there any way to configure this by default?

Thanks

commented

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.

commented

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.