Refactor action outcomes to be separate from description and notes #15380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move the outcome from being part of the description and some roll notes to having its own structured data keyed off of degree of success.
Should help reduce duplicated text in translations (description and notes) and get rid of some of the embedded formatting, which should ease the burden for translators going forward.
Includes Maneuver in Flight as an example of what changes are needed for any actions involving a check as part of its use.