Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • To clarify, when you say "merged into master", the goal of that is just to aggregate all the code changes, correct? I think I'm slightly confused since for topic branches, merging also means deleting the topic branch post-merge. Commented Aug 8, 2018 at 20:04
  • @SableDreamer Merging a branch b into master in the most general sense just means that all commits of b are now part of the history of master. Here such a merge is not strictly necessary, but it makes it more obvious that all work that was done for these releases is included on the master branch. This kind of merge is for us humans, not for git. We can use the git merge -s ours obsolete merge strategy to ignore any changes from the obsolete branch during a merge. Commented Aug 8, 2018 at 20:31
  • 3
    I would additionally point out that branches can be created from tags at any point in the future, should an unforeseen need arise, so you don't have to be 100% sure you won't ever need to add commits. Commented Aug 9, 2018 at 12:46