<!--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=593850) </details> <!--IssueSummary end--> ## Proposal Users have expressed that when using "Rebase & Merge" that it would be nice to have the option to choose between something like 'Rebase & run pipeline' and 'Merge without rerunning pipeline' To make these paths clear to users, we could introduce an additional merge detail to inform the user that rebasing will be occuring without pipelines. If they don't want this to happen then they can choose to click on "Rebase with pipeline". This effectively replaces the "Rebase source branch" button when the setting to rebase & merge is enabled. | Current | Proposal | | ------ | ------ | | {width=900 height=271} | {width=900 height=279} | ## Background Feedback - https://gitlab.com/gitlab-org/gitlab/-/work_items/895#note_3155822655 - https://gitlab.com/gitlab-org/gitlab/-/work_items/895#note_3155885509 For example without rebase & merge enabled, the user would see this - Both Rebase and "Rebase source branch" actions would rebase then run pipelines - Rebase without pipelines would only rebase {width=900 height=197} With the setting enabled, the user sees this {width=900 height=246} Yes clicking on "Merge" would rebase and merge in one click but for some teams they would like to make the option more clear that you could rebase with pipelines as a way to ensure that tests would be run against the changes holistically. In the screenshot it would be done by clicking "Rebase source branch". > [And whilst both options are still possible, it's very much pushing the user down the 'rebase and don't rerun the pipeline' option, and it's now much less apparent to the user that they should be making a decision about whether it's okay with merge without retesting](https://gitlab.com/gitlab-org/gitlab/-/work_items/895#note_3159851960:~:text=it%27s%20very%20much%20pushing%20the%20user%20down%20the%20%27rebase%20and%20don%27t%20rerun%20the%20pipeline%27%20option%2C%20and%20it%27s%20now%20much%20less%20apparent%20to%20the%20user%20that%20they%20should%20be%20making%20a%20decision%20about%20whether%20it%27s%20okay%20with%20merge%20without%20retesting)