3 ms·
Squash. PR is a github thing, not a git thing (and it’s good imo). In a PR you have description, history, and you accumulate commits as you get review(s). When
by ecesena 1y ago
Squash.
PR is a github thing, not a git thing (and it’s good imo).
In a PR you have description, history, and you accumulate commits as you get review(s).
When a PR is ready, all you need is a single commit to main, because the PR itself has the rest of the historic documentation.
- skydhash 1y agoThis. PR is just one of many methodologies with Git and has its own pros and cons. But as you said, the history is no longer so important as you have the PR reference (and can export the data). So squash it is. But for true decentralized developments, when the developer is not really part of the same organigram, I'd prefer the remote branch to be cleaned up with clear commits. in this case, I will merge.