3 ms·
> It doesn't happen to match the workflow you use? It matches the one I use. You're in the minority here. For the majority of software projects branches like `
by urda 8y ago
> It doesn't happen to match the workflow you use? It matches the one I use.
You're in the minority here. For the majority of software projects branches like `develop` are usually considered "long living" and are not "merged in" when arriving at `master`. That's why we have things like Git Flow [1].
Also an action that defaults to destroying something is user-hostile, so that's why it's a big deal and thus why GP wrote their comment.
[1] https://leanpub.com/git-flow/read
- chrisseaton 8y agoI use the feature branch Git workflow. How do you know the majority of people here use Git Flow rather than feature branches? Have you just guessed that? And anyway Git Flow still has feature branches that you close on merging!