Changes in Code Quality MR Widget Text

Release notes

Problem to solve

Improving language accuracy in Code Quality MR Widget

Intended users

User experience goal

Proposal

We want to drop the use of the word "points" completely since it's too vague and could be confused with an actual quantitative concept which is not the case. We will refer to the actual concepts instead.

Code Quality Report change

  • Code Quality scanning detected 54 changes in merged results - degradations + improvements
  • No changes to Code Quality - no changes detected in the diff
  • Failed to load Code Quality report - couldn't load the report from the target and/or source branch

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by James Heimbuck