forked from bobvanderlinden/probot-auto-merge
/
auto-merge.example.yml
101 lines (84 loc) · 4.47 KB
/
auto-merge.example.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
# Configuration for probot-auto-merge - https://github.com/bobvanderlinden/probot-auto-merge
# The minimum number of reviews from each association that approve the pull request before
# doing an automatic merge. For more information about associations see:
# https://developer.github.com/v4/enum/commentauthorassociation/
minApprovals:
MEMBER: 1
COLLABORATOR: 2
# Pull requests will only be automatically merged when all of these reviewers have approved the
# pull request.
requiredReviewers:
- rogerluan
# The maximum number of reviews from each association that request changes to the pull request.
# Setting this number higher than 0 will allow automatic merging while changes are still requested.
# Requested changes from associations not defined in this list are ignored for automatic merging.
maxRequestedChanges:
COLLABORATOR: 0
# Whether an out-of-date pull request is automatically updated.
# It does so by merging its base on top of the head of the pull request.
# This is the equivalent of clicking the 'Update branch' button.
# This is useful for repositories where protected branches are used and the option
# 'Require branches to be up to date before merging' is enabled.
# Note: this only works when the branch of the pull request resides in the same repository as
# the pull request itself.
updateBranch: true
# Whether the pull request branch is automatically deleted.
# This is the equivalent of clicking the 'Delete branch' button shown on merged pull requests.
# Note: this only works when the branch of the pull request resides in the same repository as
# the pull request itself.
deleteBranchAfterMerge: true
# In what way a pull request needs to be merged. This can be:
# * merge: creates a merge commit, combining the commits from the pull request on top of
# the base of the pull request (default)
# * rebase: places the commits from the pull request individually on top of the base of the pull request
# * squash: combines all changes from the pull request into a single commit and places the commit on top
# of the base of the pull request
# For more information see https://help.github.com/articles/about-pull-request-merges/
mergeMethod: merge
# Optionally specify the merge commit message format. The following template
# tags are supported:
# * {title}: The pull request title at the moment it is merged
# * {body}: The pull request body at the moment it is merged
# * {number}: The pull request number
# * {branch}: The name of the source branch
# * {commits}: A list of merged commits
# When this option is not set, the merge commit message is controlled by
# GitHub and uses a combination of the title of the pull request when it was
# opened (note that later changes to the title are ignored) and a list of
# commits.
# This settings is ignored when `mergeMethod` is set to `rebase`.
mergeCommitMessage: |
{title} (#{number})
{body}
# Whenever blocking base branches are configured, pull requests will only be automatically merged whenever
# their base branch (into which the PR would be merged) is not matching any regular expression listed.
blockingBaseBranches:
- trunk
- regex: ^dev-
# Whenever required base branches are configured, pull requests will only be automatically merged whenever
# their base branch (into which the PR would be merged) is matching any regular expression listed.
requiredBaseBranches:
- master
# Blocking labels are the labels that can be attached to a pull request to make sure the pull request
# is not being automatically merged.
blockingLabels:
- blocked
# Similar to `blockingLabels`, except these will be matched as case insensitive regular expressions,
# instead of looking for exact matches like the `blockingLabels` option.
blockingLabelsRegex:
- (.*)block(.*)
# Whenever required labels are configured, pull requests will only be automatically merged whenever
# all of these labels are attached to a pull request.
requiredLabels:
- merge
# Similar to `requiredLabels`, except these will be matched as case insensitive regular expressions,
# instead of looking for exact matches like the `requiredLabels` option.
requiredLabelsRegex:
- (.*)approved(.*)
# Pull requests will only be automatically merged if there is a match between the regular expression
# and its title
requiredTitleRegex: '\bmerge\b'
# Automatic merges will be blocked if there is a match between the regular expression and title
blockingTitleRegex: '\bwip\b'
# Automatic merges will be blocked if there is a match between the regular expression and body
blockingBodyRegex: '\bDo not merge\b'