<!--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=22036) </details> <!--IssueSummary end--> - In Looker, when you make changes to a development branch, you can check if your changes pass validation (and the UI runs the validator somewhat automatically). - As part of the development workflow, you don't want to merge any changes, unless those have been validated. - So we should expose that validation back in the GitLab merge request, via the Looker API: https://docs.looker.com/reference/api-and-integration/api-reference/project#validate_project - Essentially, this is replicating the functionality of blocking a merge from happening unless the pipeline passed. Instead of the pipeline, we check the Looker validation. - Similarly, we can replicate MWPS, but with merge-when-looker-validates.