4 ms·
> closing development branch when you merge into master??? Why's that a horrible default? It doesn't happen to match the workflow you use? It matches the one I
by chrisseaton 8y ago
> closing development branch when you merge into master???
Why's that a horrible default? It doesn't happen to match the workflow you use? It matches the one I use. So I can understand it's not ideal for you but they can't suit everyone with a binary default so what makes it so 'horrible'?
- twblalock 8y agoGithub handles it better. It lets you decide whether or not to close the branch, lets you protect certain branches from being closed, etc.
- pnloyd 8y agoBitbucket I use gives you the option as a checkbox upon merging.
- greglindahl 8y agoSo, if my company has a workflow where that box should always be checked or not, and rarely overridden by the user, ...
- another-cuppa 8y agoRemember Atlassian in their infinite wisdom renamed the on-premises product formerly known as Stash to Bitbucket despite being a completely different code base to Bitbucket.com. I think they are talking about Bitbucket.com.
- leoedin 8y agoThe bitbucket.com website gives a check box to select whether to close a branch though. Unless you mean that the on-premises product doesn't?
- another-cuppa 8y agoThe on-prem one I use has checkbox when you merge. It's unticked by default.
- gpm 8y agoThe on prem version I was using a month ago had a checkbox, ticked the last way you checked it by default. So if you merged feature -> develop -> master and remembered to delete feature it would delete develop by default as well...
- briandear 8y agoA default should not do something destructive or pseudo-destructive. That’s pretty much against most UX standards.
- 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!