For more details please read the parent Epic https://gitlab.com/groups/gitlab-org/-/epics/3869+ ### Proposal [Block merges of merge requests unless all status checks have passed](https://docs.gitlab.com/ee/user/project/merge_requests/status_checks.html#block-merges-of-merge-requests-unless-all-status-checks-have-passed) was introduced in 15.9. This epic is a follow up to add some specific QOL features. Currently when a status check is started there is no indication that the request is in process, and there is no timeout so the status checks can continue to "hang" unless it receives a error response. We want to add a explicit pending state and timeout so that users have clear indication of the current state of the status check, and they can retry easily or change as needed. ### Designs Pending  Retry  <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->