Implementing Azure DevOps Solutions

Squash commit

When performing a so-called squash commit, you are combining all of the individual commits from the source branch in one, new commit. This is useful when all of the commits on the source branch relate to one feature and you want to keep a clear, concise change history on the target branch. Especially when there are commits with bugfixes or clean-up operations on the source branch, this approach makes sense. The disadvantage is that you might lose the rationale for some incremental changes that were made on the source branch.