@pfm Each commit should be an atomic change with an informative commit message. If you have multiple commits in your feature branch because you cleaned up your code or fixed bugs, then it's fine to squash it into a single commit. You should not squash commits which make unrelated changes into a single commit.
I often find myself looking at git blame to figure out why a part of code was changed, and if the commit I find comprises of 10 squashed commits, then it's difficult or impossible to tell.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!