Skip to content

Refactor of quality checks part 1 #206

@iw-ezequiel

Description

@iw-ezequiel

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?

Originally posted by @andyblundell in #163 (review)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions