On Tue, May 26, 2026 at 2:16 PM Esme Povirk <esme@codeweavers.com> wrote:
If it matters, I actually do use the GitLab UI to do merges.
However, the GitLab UI discourages using it for rebases, linking to this page: https://gitlab.winehq.org/help/ci/pipelines/merge_request_pipelines.html#run...
Therefore, I do not use the GitLab UI to do rebases. Does the new version address this somehow?
If I understand that page correctly, it's just saying that merge requests can introduce malicious code that is run as part of the test suite before the merge request is actually merged. GitLab is just trying to warn you to not do test runs on untrusted code, and warn you that you clicking "Rebase" will automatically trigger a test run even if the merge request's author does not have permissions to do a test run. If you want to rebase without doing a test run, there is a separate "Rebase without pipeline" button on the merge request. The "automatic rebase" option that I'd like to enable effectively clicks "Rebase without pipeline" for you when you click "Merge".[1] I think the new option would be perfect for your workflow. -Alex [1] https://docs.gitlab.com/19.0/user/project/merge_requests/methods/#automatic-...