<!--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=24365) </details> <!--IssueSummary end--> ### Problem to solve When Trunk based development we occure some problems in pipelines. During our pipline there are many commits that starts another pipelines. When any of those fails its hard to find out which couse the problem. ### Further details When many developers works on same repository and there are many commits during one hour, and every day Wy must find failed. Developer make changes and goes to other task when he gets back there is many failed pipes and we don't know what failed exacly, We don't want to allow commit wrong changes ### Proposal We would like to deny applying failed commits by auto revert or precommit. We would like to test changes and after it failes is should be revert, or in case precommit when it success should be marged. ### What does success look like, and how can we measure that? Like I wrote above ^^ ### Links / references