We currently don't have a clear guideline on the preferred git strategy. I noticed @milancurcic recently switched from merge commits to squash on merge to add patches to the default branch. I'm personally a big fan of linear repository histories and a regular user of the git rebase feature, but I know of developers and long-term git users not sharing this preference. So far I didn't see any opposition against squashing commits on merge here, still I think it could use some discussion or at least some documentation.

Should we have a clear recommendation on the git strategy? Even if we don't agree on a preferred strategy, should we document general recommendations for working with git? What do you think?

For reference some development guides that are explicitly discussing git strategies:

The DFTB+ developer guide has an explicit section on merging patches, with a strong preference for merge commits
https://dftbplus-develguide.readthedocs.io/en/latest/maintainerflow.html#merging-strategy

And explicit recommendations when to use or avoid git rebase
https://dftbplus-develguide.readthedocs.io/en/latest/gitworkflow.html#merge-the-changes-back-into-the-upstream-repository

Meson's development guide discusses merging of patches as well, with a strong preference for rebasing
https://mesonbuild.com/Contributing.html#strategy-for-merging-pull-requests-to-trunk