1
+ # ###############################################################################
2
+ # Licensed to the Apache Software Foundation (ASF) under one
3
+ # or more contributor license agreements. See the NOTICE file
4
+ # distributed with this work for additional information
5
+ # regarding copyright ownership. The ASF licenses this file
6
+ # to you under the Apache License, Version 2.0 (the
7
+ # "License"); you may not use this file except in compliance
8
+ # with the License. You may obtain a copy of the License at
9
+ #
10
+ # http://www.apache.org/licenses/LICENSE-2.0
11
+ #
12
+ # Unless required by applicable law or agreed to in writing, software
13
+ # distributed under the License is distributed on an "AS IS" BASIS,
14
+ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15
+ # See the License for the specific language governing permissions and
16
+ # limitations under the License.
17
+ # ###############################################################################
18
+
19
+ labelPRBasedOnFilePath :
20
+ component=BuildSystem :
21
+ - .github/**/*
22
+ - tools/maven/*
23
+
24
+ component=Documentation :
25
+ - docs/**/*
26
+
27
+ component=Connectors/Redis :
28
+ - src*/**/*
29
+
30
+ # ##### IssueLink Adder #################################################################################################
31
+ # Insert Issue (Jira/Github etc) link in PR description based on the Issue ID in PR title.
32
+ insertIssueLinkInPrDescription :
33
+ # specify the placeholder for the issue link that should be present in the description
34
+ descriptionIssuePlaceholderRegexp : " ^Issue link: (.*)$"
35
+ matchers :
36
+ # you can have several matches - for different types of issues
37
+ # only the first matching entry is replaced
38
+ jiraIssueMatch :
39
+ # specify the regexp of issue id that you can find in the title of the PR
40
+ # the match groups can be used to build the issue id (${1}, ${2}, etc.).
41
+ titleIssueIdRegexp : \[(FLINK-[0-9]+)\]
42
+ # the issue link to be added. ${1}, ${2} ... are replaced with the match groups from the
43
+ # title match (remember to use quotes)
44
+ descriptionIssueLink : " [${1}](https://issues.apache.org/jira/browse/${1}/)"
45
+ docOnlyIssueMatch :
46
+ titleIssueIdRegexp : \[hotfix\]
47
+ descriptionIssueLink : " `Documentation only change, no JIRA issue`"
48
+
49
+ # ##### Title Validator #################################################################################################
50
+ # Verifies if commit/PR titles match the regexp specified
51
+ verifyTitles :
52
+ # Regular expression that should be matched by titles of commits or PR
53
+ titleRegexp : ^\[FLINK-[0-9]+\].*$|^\[FLINK-XXXXX\].*$|^\[hotfix].*$
54
+ # If set to true, it will always check the PR title (as opposed to the individual commits).
55
+ alwaysUsePrTitle : false
56
+ # If set to true, it will only check the commit in case there is a single commit.
57
+ # In case of multiple commits it will check PR title.
58
+ # This reflects the standard behaviour of Github that for `Squash & Merge` GitHub
59
+ # uses the PR title rather than commit messages for the squashed commit ¯\_(ツ)_/¯
60
+ # For single-commit PRs it takes the squashed commit message from the commit as expected.
61
+ #
62
+ # If set to false it will check all commit messages. This is useful when you do not squash commits at merge.
63
+ validateEitherPrOrSingleCommitTitle : true
64
+ # The title the GitHub status should appear from.
65
+ statusTitle : " Title Validator"
66
+ # A custom message to be displayed when the title passes validation.
67
+ successMessage : " Validation successful!"
68
+ # A custom message to be displayed when the title fails validation.
69
+ # Allows insertion of ${type} (commit/PR), ${title} (the title validated) and ${regex} (the titleRegexp above).
70
+ failureMessage : " Wrong ${type} title: ${title}"
71
+
72
+ # Various Flags to control behaviour of the "Labeler"
73
+ labelerFlags :
74
+ # If this flag is changed to 'false', labels would only be added when the PR is first created
75
+ # and not when existing PR is updated.
76
+ # The default is 'true' which means the labels would be added when PR is updated even if they
77
+ # were removed by the user
78
+ labelOnPRUpdates : true
79
+
80
+ # Comment to be posted to welcome users when they open their first PR
81
+ firstPRWelcomeComment : >
82
+ Thanks for opening this pull request! Please check out our contributing guidelines. (https://flink.apache.org/contributing/how-to-contribute.html)
83
+
84
+ # Comment to be posted to congratulate user on their first merged PR
85
+ firstPRMergeComment : >
86
+ Awesome work, congrats on your first merged pull request!
0 commit comments