Common cases where a pull request would not be merged automatically by Auto-Merge:
-
The pull request author misses permission to merge to destination repository.
-
Auto-merge feature is disabled in destination repository of pull request.
-
Last build of pull request is still in progress or has failed.
-
Someone selected “needs work” for their review status
-
Pull request title is not prefixed with
[AUTO]- or[SHIP]/[SHOW]if Ship/Show/Ask feature enabled. -
Before version 6.7.0:
If a merge check does requests to a 3rd party system (like Jira), then the Auto-Merge Bitbucket service user might not have permissions to do it, causing the auto-merge to fail. This is a known situation when using the merge check “Require that a pull request is associated with a valid Jira issue” from ScriptRunner for Bitbucket. We are working on a way to configure a separate Bitbucket user for auto-merging, please vote on CODEOWNERS-56.-
Since version 6.7.0, the pull request author is used to the perform the merge.
-