<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=533954) </details> <!--IssueSummary end--> ## Proposal Use color on the badges to help differentiation of the different merge requests. | Badge | Assignee/author actions | Reviewer actions | | ------ | ------ | ------ | | neutral-muted (gray) | `Waiting for approval`, `# approval required` | `# approval required`, `You requested changes`, `You commented`, `Approved` | | warning (yellow) | `Draft`, `Reviewers needed` | `Requested` | | info (blue) | `Reviewer commented` | `Review started` | | error (red) | `Changes requested` | | | success (green) | `Ready to merge` | | ## Background We have already started introducing the `success` (green) badges when merge checks have passed in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/183524 Feedback received that this would be useful 1. https://gitlab.com/gitlab-org/gitlab/-/issues/512314#note_2296778901 2. https://gitlab.com/gitlab-org/gitlab/-/issues/512314#note_2298862467 3. https://gitlab.com/gitlab-org/gitlab/-/issues/457731#note_2428524566 4. [3400#color-action-status-help-identify-what-needs-your-attention](https://gitlab.com/gitlab-org/ux-research/-/issues/3400#color-action-status-help-identify-what-needs-your-attention)