Skip to content
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

Git flow configuration #6448

Open
Narven opened this issue Oct 1, 2019 · 2 comments
Open

Git flow configuration #6448

Narven opened this issue Oct 1, 2019 · 2 comments

Comments

@Narven
Copy link

Narven commented Oct 1, 2019

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

@reshadf
Copy link

reshadf commented Jan 27, 2020

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
Copy link

m4l490n commented Jun 5, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants