UI for merge request widget to rebase without triggering CI
This followup issue is for the UI feature of the API implemented in #38141 (closed)
Release notes
For large monorepos with semi-linear branching and many devs working out of the same repo rebasing without running CI is possible through commit messages and the API but not the UI. This means you have to run a pipeline which takes time and uses runner minutes.
Now you can get the same rebase with ci skip functionality in the Merge Request to rebase your branch without having to run a pipeline.
Problem to solve
For large monorepos with semi-linear branching and many devs working out of the same repo, rebases are quite common and cause the pipeline to run repeatedly which is not desirable.
It was already possible to skip the creation of a CI pipeline when using ci skip (or skip ci) in your commit message or by using push options and through the API, but it is not possible to skip CI when rebasing through the UI.
Intended users
Further details
Proposal
Add the ability in the UI for the merge request widget to rebase without triggering CI. The rebase button when offered will be converted to a primary info split dropdown button with the additional options stating:
RebaseRebase without triggering CI
Note: The ability to send in a skip ci flag on the api call for a MR rebase is implemented in #38141 (closed)
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
This feature is currently gated with a feature flag implemented in !78194 (merged)
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.