Squash Merge

Mon, 01 Jan 0001 00:00:00 +0000

A squash merge collapses every commit on a feature branch into a single new commit on the target branch. Instead of replaying the branch’s history one commit at a time, Git combines all of the branch’s changes into one diff and lands that as a lone commit. The original per-commit history of the branch is discarded from the target branch’s record.

It is the workflow of choice when the branch’s intermediate commits are noise – “wip”, “fix typo”, “address review” – and only the net change is worth keeping in the permanent history.

Submitting a PR to a Third-Party Repo

Mon, 01 Jan 0001 00:00:00 +0000

Opening a pull request against someone else’s open source project is as much a social act as a technical one. You are asking a maintainer – usually an unpaid volunteer with a backlog – to read your change, trust it, and take on the burden of maintaining it forever. The best contributions minimize that burden: they are small, they follow the project’s existing conventions, and they arrive with enough context that the maintainer can say yes without a second round of questions. This page is an opinionated checklist for getting a change merged into a repository you don’t control.

Git on Bitsy Services Wiki

Squash Merge

Submitting a PR to a Third-Party Repo