This is an automated email from the ASF dual-hosted git repository.
martijnvisser pushed a commit to branch main
in repository
https://gitbox.apache.org/repos/asf/flink-connector-elasticsearch.git
The following commit(s) were added to refs/heads/main by this push:
new e0b1d27 [FLINK-27062][Connector/Elasticsearch][Buildsystem] Enable
Boring Cyborg for flink-connector-elasticsearch
e0b1d27 is described below
commit e0b1d279e2cf5f521da30b18d6fe576363ce1c60
Author: MartijnVisser <[email protected]>
AuthorDate: Tue Apr 5 17:50:37 2022 +0200
[FLINK-27062][Connector/Elasticsearch][Buildsystem] Enable Boring Cyborg
for flink-connector-elasticsearch
---
.github/boring-cyborg.yml | 67 +++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 67 insertions(+)
diff --git a/.github/boring-cyborg.yml b/.github/boring-cyborg.yml
new file mode 100644
index 0000000..9030044
--- /dev/null
+++ b/.github/boring-cyborg.yml
@@ -0,0 +1,67 @@
+################################################################################
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+################################################################################
+
+labelPRBasedOnFilePath:
+ component=BuildSystem:
+ - .github/**/*
+
+ component=Documentation:
+ - docs/**/*
+
+ component=Connectors/Elasticsearch:
+ - flink-connector-elasticsearch*/**/*
+ - flink-sql-connector-elasticsearch*/**/*
+
+###### Title Validator
#################################################################################################
+# Verifies if commit/PR titles match the regexp specified
+verifyTitles:
+ # Regular expression that should be matched by titles of commits or PR
+ titleRegexp: ^\[FLINK-[0-9]\].*$|^\[FLINK-XXXXX\].*$|^\hotfix.*$
+ # If set to true, it will always check the PR title (as opposed to the
individual commits).
+ alwaysUsePrTitle: true
+ # If set to true, it will only check the commit in case there is a single
commit.
+ # In case of multiple commits it will check PR title.
+ # This reflects the standard behaviour of Github that for `Squash & Merge`
GitHub
+ # uses the PR title rather than commit messages for the squashed commit
¯\_(ツ)_/¯
+ # For single-commit PRs it takes the squashed commit message from the commit
as expected.
+ #
+ # If set to false it will check all commit messages. This is useful when you
do not squash commits at merge.
+ validateEitherPrOrSingleCommitTitle: true
+ # The title the GitHub status should appear from.
+ statusTitle: "Title Validator"
+ # A custom message to be displayed when the title passes validation.
+ successMessage: "Validation successful!"
+ # A custom message to be displayed when the title fails validation.
+ # Allows insertion of ${type} (commit/PR), ${title} (the title validated)
and ${regex} (the titleRegexp above).
+ failureMessage: "Wrong ${type} title: ${title}"
+
+# Various Flags to control behaviour of the "Labeler"
+labelerFlags:
+ # If this flag is changed to 'false', labels would only be added when the PR
is first created
+ # and not when existing PR is updated.
+ # The default is 'true' which means the labels would be added when PR is
updated even if they
+ # were removed by the user
+ labelOnPRUpdates: false
+
+# Comment to be posted to welcome users when they open their first PR
+firstPRWelcomeComment: >
+ Thanks for opening this pull request! Please check out our contributing
guidelines. (https://flink.apache.org/contributing/how-to-contribute.html)
+
+# Comment to be posted to congratulate user on their first merged PR
+firstPRMergeComment: >
+ Awesome work, congrats on your first merged pull request!
