-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Implement the explicit automergeStrategy for the GitHub platform. #10869
Copy link
Copy link
Labels
core:automergeRelating to Renovate's automerge capabilitiesRelating to Renovate's automerge capabilitiesplatform:githubGitHub PlatformGitHub Platformpriority-2-highBugs impacting wide number of users or very important featuresBugs impacting wide number of users or very important features
Metadata
Metadata
Assignees
Labels
core:automergeRelating to Renovate's automerge capabilitiesRelating to Renovate's automerge capabilitiesplatform:githubGitHub PlatformGitHub Platformpriority-2-highBugs impacting wide number of users or very important featuresBugs impacting wide number of users or very important features
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 GitHub platform, allowing users to configure the explicit merge strategy used by Renovate when automerging pull requestsDid you already have any implementation ideas?
The optional
MergeStrategyargument can be provided to the GitHubmergePrimplementation.The current implementation uses the merge strategy configured on the repository at the time it is internally constructed, with preferences based on which features are allowed. The Renovate-specific strings for automergeStrategy can be mapped to GitHub-specific strings when submitting the merge request to GitHub or aborted if the configured strategy is not listed as available.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/github/index.mdand update the description indocs/usage/configuration-options.mdif necessary.