> Then once approved, we click the "squash and merge" button, and github squashes all that useless noise into a single commit on master for us. This is not wha

> Then once approved, we click the "squash and merge" button, and github squashes all that useless noise into a single commit on master for us. This is not what squash is. I suggest you to read again the section "What squash merge actually is". tl;dr: "Squash merge is the same as the true merge but with a missing information: the reference to the merged branch." > We don't have any complaints about this workflow. Repeating the same answer: Just because you never had doesn't mean that they don't exist. If you saw it at least once, it means that it exists. I saw it once, and I related here: https://lucasoshiro.github.io/posts-en/2024-06-27-squash-submodule/ https://lucasoshiro.github.io/posts-en/2024-06-27-squash-sub...