<!--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=24490) </details> <!--IssueSummary end--> ### Problem to solve I've noticed Gitlab uses the Dangerfile in all relevant projects, and has a bot in each project to pull the results of the Dangerfile to the Merge Request discussions. It'd be better if this was in line with SAST, DAST, Build Pipeline results (up top, with green checkmarks). ### Further details We want to use something like Dangerfile, but it _has_ to be followed and easy to use / spot. ### Proposal * Move the results of a Danger check to the top of the MR so it's easily visible, and possibly even a thing that Reviewers have to actively click "accept / bypass" on. ### What does success look like, and how can we measure that? I imagine adding a block here. Maybe do like Github and collapse some of these into a common "reviews" block.  ### Links / references