-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Implement the explicit automergeStrategy for the Gitlab platform. #10870
Copy link
Copy link
Open
Labels
core:automergeRelating to Renovate's automerge capabilitiesRelating to Renovate's automerge capabilitiesplatform:gitlabGitLab PlatformGitLab Platformpriority-4-lowLow priority, unlikely to be done unless it becomes important to more peopleLow priority, unlikely to be done unless it becomes important to more people
Metadata
Metadata
Assignees
Labels
core:automergeRelating to Renovate's automerge capabilitiesRelating to Renovate's automerge capabilitiesplatform:gitlabGitLab PlatformGitLab Platformpriority-4-lowLow priority, unlikely to be done unless it becomes important to more peopleLow priority, unlikely to be done unless it becomes important to more people
Type
Fields
Give feedbackPriority
None yet
Datasource
None yet
What would you like Renovate to be able to do?
The
automergeStrategyconfiguration item introduced in #10627 should be implemented for the Gitlab platform, allowing users to configure the explicit merge strategy used by Renovate when automerging merge requestsDid you already have any implementation ideas?
The optional
MergeStrategyargument can be provided to the GitLabmergePrimplementation. The current implementation relies on GitLab using a "merge"-like strategy by default. The Renovate-specific strings forautomergeStrategy=squashcan be mapped to the parametersquashwhen submitting the accept-merge request to GitLab. It's not immediately clear if any other explicit strategies are supported by GitLab at time of writing.If #10830 has been implemented, the arguments to
mergePrmay be different than what has been listed here. We should also remember to clean up the missing feature notice inlib/platform/gitlab/index.mdand update the description indocs/usage/configuration-options.mdif necessary.