Skip to content

Conversation

joyceerhl
Copy link

For #12867

Don't increase model change count when trust updates

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
  • Title summarizes what is changing.
  • Has a news entry file (remember to thank yourself!).
  • Appropriate comments and documentation strings in the code.
  • Has sufficient logging.
  • Has telemetry for enhancements.
  • Unit tests & system/integration tests are added/updated.
  • Test plan is updated as appropriate.
  • package-lock.json has been regenerated by running npm install (if dependencies have changed).
  • The wiki is updated with any design decisions/details.

@joyceerhl joyceerhl added the no-changelog No news entry required label Jul 12, 2020
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@joyceerhl joyceerhl requested review from a team, DavidKutu, DonJayamanne, IanMatthewHuff and rchiodo and removed request for a team July 12, 2020 04:00
// Dirty state comes from undo. At least VS code will track it that way. However
// skip file changes as we don't forward those to VS code
if (change.kind !== 'save' && change.kind !== 'saveAs') {
if (change.kind !== 'save' && change.kind !== 'saveAs' && change.kind !== 'updateTrust') {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this is one of those where a test would have been good. No need of tests now.

@joyceerhl joyceerhl merged commit ebcc840 into microsoft:master Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog No news entry required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants