<!--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=229137) </details> <!--IssueSummary end--> ### Problem to solve I use the [Pipeline API](https://docs.gitlab.com/ee/api/pipelines.html#list-project-pipelines) to get a list of the latest pipeline states for a project. This response includes a status for each pipeline. The list returns "success" in case the pipeline passed successful. It returns the same status however even if warnings occurred. These are two different things imho. This is in contrast to the GUI and badges. The GUI shows "Passed with Warnings" as label and a yellow color if the pipeline passed with warnings. Instead of "Passed" as label and green color if the pipeline was successful without warnings. The badge buttons show a different color as well.  I can not get the same result using the Pipeline API endpoint right now. Is it possible to reflect the "warnings" in the Pipeline API endpoint right away? ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### User experience goal Get the same „distinct“ pipeline state in the GUI, badges and API list. ### Proposal Return a list with all pipelines **and** “distinct” states. E.g. an extra field `"status_has_warnings": true` ### Permissions and Security No security impact imho. ### Documentation List Pipelines Endpoint: https://docs.gitlab.com/ee/api/pipelines.html#list-project-pipelines ### Availability & Testing * Unit test changes required * Integration test changes required ### What does success look like, and how can we measure that? … ### What is the type of buyer? … ### Is this a cross-stage feature? … ### Links / references …