ALM Toolkit changes code order and marks everything as change. You lose track of changes

[marius061]

Example:
I want to add a new table to my Dev-semantic-model and than push this change to my Prod-semantic-model. The ALM-Toolkit marks this table as a change. The Problem is that sometimes the Tool switches the order of the semantic model definition so that things are marked as changes which arent. It makes it very hard to recognize which are my real changes and which not and I have to analyse all marked changes because I don't wont to deploy a change from another person in my deployment.
So when I make a little change I have to check like 50 places to proof that I deploy only my change!

Thank you for your help!!

[christianwade]

Thanks for raising. This looks to be due to a known issue called "TMDL spurious diffs" that is documented with workaround at the bottom of the ALM Toolkit documentation and at #297 (comment).