The drawback is the fact that changes to the commit history of the master branch are often rejected by tools like GitLab and GitHub due to the possibility that a master git rebase can negatively ...

When your git commit history gets long in the tooth, and you want to clean up your feature and topic branches before the merge to master, you’ll need the facilities of the Git squash commit feature.

As a result, anyone could, for example, commit to master, reopen and close issues in Issue Tracker, or even wipe the entire history of any GitHub project.