-
Notifications
You must be signed in to change notification settings - Fork 41
Clarification/context #163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Some added context and clarification around the definitions of green/amber
andyblundell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To move this forward, how about we apply the general wording changes to the "usage" section in a brand new PR first, then we have another look at the table changes? I wouldn't mind including the this-is-what-red-really-means view of risks in the list too, which might be another good reason for formatting this a different way (not a table?) - and maybe we could do all of those table changes at the same time?
Have created #207 for this, will leave this PR open in the meantime so as to cross-reference but will close once we've pulled all the content we need (because of the table it's kind of impossible to meaningfully cherry-pick anything!). |
|
Kudos, SonarCloud Quality Gate passed! |
|
Dependabot Alert SummaryTotal open alerts: 0 ✅ All alerts are within acceptable age thresholds |
|
Having resolved the merge conflicts, the majority of this PR has made its way in via other means. Closing. |











Some added context and clarification around the definitions of green/amber