Hacker News new | ask | show | jobs
by cmurphycode 2178 days ago
This is close enough to what we do -- and it works -- but since we support multiple releases at a time, it often ends up feeling like merging is pointless. Merging a dev branch into trunk feels good, but honestly most git interactions involve cherry-picking sets of commits to old releases, or to create hotfixes (So much, in fact, that we built some tooling around it to make it easier to not screw up). So then, you start to wonder, why am I special casing this one situation and using merge to trunk, and using cherry pick everywhere else.
1 comments

I cherry pick (or rebase, usually) to master, too. I only merge when I'm actually merging divergent histories.