Or you could make consideration for tracking that change in source code a priority when making those changes and code appropriately. The problem you describe i

Or you could make consideration for tracking that change in source code a priority when making those changes and code appropriately. The problem you describe is a problem because people are not prioritizing or valuing the commit history as a resource. If you fix that, then people will think about these things differently. Squash and merge is not the only way to get things into master. You can rebase and squash commits as needed on your branch and then bring multiple commits from your branch onto master. That takes more advanced usage of git, but learning that makes sense once you start really valuing the history.