microsoft / microsoft/Analysis-Services
ALM Toolkit changes code order and marks everything as change. You lose track of changes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 732
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
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!!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported workflow in ALM Toolkit: add a table to the Dev semantic model and compare it with the Prod semantic model. Use the attached examples to identify cases where definition order changes and unrelated items are marked as changes. Done means the intentional table addition is distinguishable without reviewing many unrelated changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100