|
| 1 | +# Configuration for probot-auto-merge - https://github.com/bobvanderlinden/probot-auto-merge |
| 2 | + |
| 3 | +# The minimum number of reviews from each association that approve the pull request before |
| 4 | +# doing an automatic merge. For more information about associations see: |
| 5 | +# https://developer.github.com/v4/reference/enum/commentauthorassociation/ |
| 6 | +minApprovals: |
| 7 | + MEMBER: 0 |
| 8 | + COLLABORATOR: 0 |
| 9 | + |
| 10 | +# The maximum number of reviews from each association that request changes to the pull request. |
| 11 | +# Setting this number higher than 0 will allow automatic merging while changes are still requested. |
| 12 | +# Requested changes from associations not defined in this list are ignored for automatic merging. |
| 13 | +maxRequestedChanges: |
| 14 | + COLLABORATOR: 0 |
| 15 | + |
| 16 | +# Whether an out-of-date pull request is automatically updated. |
| 17 | +# It does so by merging its base on top of the head of the pull request. |
| 18 | +# This is the equivalent of clicking the 'Update branch' button. |
| 19 | +# This is useful for repositories where protected branches are used and the option |
| 20 | +# 'Require branches to be up to date before merging' is enabled. |
| 21 | +# Note: this only works when the branch of the pull request resides in the same repository as |
| 22 | +# the pull request itself. |
| 23 | +updateBranch: true |
| 24 | + |
| 25 | +# Whether the pull request branch is automatically deleted. |
| 26 | +# This is the equivalent of clicking the 'Delete branch' button shown on merged pull requests. |
| 27 | +# Note: this only works when the branch of the pull request resides in the same repository as |
| 28 | +# the pull request itself. |
| 29 | +deleteBranchAfterMerge: true |
| 30 | + |
| 31 | +# In what way a pull request needs to be merged. This can be: |
| 32 | +# * merge: creates a merge commit, combining the commits from the pull request on top of |
| 33 | +# the base of the pull request (default) |
| 34 | +# * rebase: places the commits from the pull request individually on top of the base of the pull request |
| 35 | +# * squash: combines all changes from the pull request into a single commit and places the commit on top |
| 36 | +# of the base of the pull request |
| 37 | +# For more information see https://help.github.com/articles/about-pull-request-merges/ |
| 38 | +mergeMethod: merge |
| 39 | + |
| 40 | +# Blocking labels are the labels that can be attached to a pull request to make sure the pull request |
| 41 | +# is not being automatically merged. |
| 42 | +blockingLabels: |
| 43 | +- blocked |
| 44 | + |
| 45 | +# Whenever required labels are configured, pull requests will only be automatically merged whenever |
| 46 | +# all of these labels are attached to a pull request. |
| 47 | +requiredLabels: |
| 48 | +- merge |
| 49 | + |
| 50 | +# Automatic merges will be blocked if there is a match between the regular expression and title |
| 51 | +blockingTitleRegex: '\bwip\b' |
| 52 | + |
| 53 | +# The status of the auto-merge process will be shown in each PR as a check. This can be especially useful to find out why a PR is not being merged automatically. |
| 54 | +reportStatus: true |
0 commit comments