Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I struggle to think of any use cases for merging from. Why was the merge command designed this way? The model here is that many developers on the same project are using branches to develop fea...
Answer
#1: Initial revision
by
Karl Knechtel
·
2023-08-09T01:15:49Z (over 1 year ago)
> I struggle to think of any use cases for merging *from*. Why was the merge command designed this way? The model here is that many developers on the same project are using branches to develop features independently; someone has to be in charge, and that is the person responsible for the `master` (release) branch that will be used to tag, package and distribute releases of the software. From *that* person's perspective, merges are naturally *into* the same branch, which is practically always the destination. It's the source that needs to be specified, because it's the source that *varies*.