Closed ghost closed 2 years ago
The merge options are typically a team decision alongside what makes the most sense for automated delivery. There are a couple camps of thought: rebase
users like a linear commit history, and merge
users who prefer less risk of conflict.
It doesn't really matter tor our work, we'll be able to "undo" any breaking changes using revert
or reset
. Personally, I prefer to make a bunch of atomic commits in a pull request (aka PR), and set the repositories settings to only make the squash merge option available in PRs. GitHub will automatically collapse all my commit's into a single merge commit.
On GitHub, once you open a pull request, if you have the correct permissions, you can "Squash Before Merging". Gonna leave this one up to Tim whether this is something worth learning now.