Define the anatomy of a good error message
In the work @pedroms and I have been doing for devopscreate, we've created a working standard for the structure of error / warning / status messages in the merge request widget. We believe it's useful in general, not just for the widget Create oversees, but we need to document it in Pajamas.
In short:
[status]: [explanation] [next step] [optional link to docs or other resource]
Pedro, what do we need to do next? I'm a little unsure of my footing here, but I assume we'll want to make changes to https://design.gitlab.com/components/alert#content.
Related links
- Related to gitlab-org/create-stage#12955 (closed) where Pedro and I discussed getting this issue in place
- Related to gitlab-org&6436 the epic where we're tracking all of the work
- Related to gitlab-org/gitlab#346051 (closed) tracking the changes landed in 14.5
- Related to gitlab-org/gitlab#346053 (closed) tracking the changes landed in 14.6