Workflow docs don't explain how to squash commits
I've been following the workflow docs and running into some trouble:
https://musescore.org/en/handbook/developers-handbook/finding-your-way-…
If you follow the docs as they are, you will be submitting unsquashed commits. Given that Musescore wants you to squash your commits, it would be very useful to include a step explaining how to do this.
Comments
You mean something like the "squash your commits" section under "Advise & Tips" on that very same page?
https://musescore.org/en/handbook/developers-handbook/finding-your-way-…
There is actually some value to having code changes divided up into small commits when the PR is submitted as this makes the review easier, even if the commits are to be squashed later on before it gets merged.
It would be great if Git had the notation of a "super commit" - a group of commits that appear as a single commit in the log, but can be separated again later if desired.