<!--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=205406) </details> <!--IssueSummary end--> ### Problem to solve We need owners to be able to merge failed pipelines even though "Pipelines must succeed" is enabled. ### Intended users Lead Developers with ownership of the repo ### Further details Yesterday our GitHub implementation was replaced with GitLab. One feature we noticed right away was missing was the possibility for owners/administrators to merge failed pipelines if "Pipelines must succeed" was enabled. This was possible in GitHub and we've used the feature quite a lot due to flaky tests. It could be Network issues, API issues, Protractor/Selenium, etc. So let's say 1 out of 800 tests fails. Well, tough luck. You can't merge, even though you are the owner of the repo. So instead of just force merge, since you know which tests can fail, you have to run tests for another 30 minutes, just to se another random test fail. Yes, in a perfect world you wouldn't merge stuff with failing tests, or use another test framework that allows the pipeline to be green when a flaky test fails. But that's besides the point. As an owner I should be able to merge, even though the developers can't. This is helpful in the case of a normal pipeline taking 1+ hours and your trying to get out a fix quickly.  ### Proposal Add an option to allow owners to merge failed pipeline when "Pipelines must succeed" is enabled. Could just be a simple checkbox under "Pipelines must succeed" option. #### Proposal considerations As noted in #4161 Anytime you let someone merge outside the normal channels it can create compliance issues. Some considerations/options/constraints we should think about when deciding on the MVC for this are: 1. only allow this on non-protected branches 1. only allow if approval rule allows it 1. only allow this on projects without compliance pipelines 1. log any force merge to the audit log for compliance purposes ("audit log" being a thing I just made up) ### Permissions and Security Only owners can enable this. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references