|
| 1 | +# boring-cyborg.yml |
| 2 | +# https://probot.github.io/apps/boring-cyborg/ |
| 3 | + |
| 4 | +##### Labeler ########################################################################################################## |
| 5 | +## Enable "labeler" for your PR that would add labels to PRs based on the paths that are modified in the PR. |
| 6 | +#labelPRBasedOnFilePath: |
| 7 | +# # Add 'label1' to any changes within 'example' folder or any subfolders |
| 8 | +# label1: |
| 9 | +# - example/**/* |
| 10 | +# |
| 11 | +# # Add 'label2' to any file changes within 'example2' folder |
| 12 | +# label2: |
| 13 | +# - example2/* |
| 14 | +# |
| 15 | +# # Complex: Add 'area/core' label to any change within the 'core' package |
| 16 | +# area/core: |
| 17 | +# - src/core/* |
| 18 | +# - src/core/**/* |
| 19 | +# |
| 20 | +# # Add 'test' label to any change to *.spec.js files within the source dir |
| 21 | +# test: |
| 22 | +# - src/**/*.spec.js |
| 23 | +# |
| 24 | +# Various Flags to control behaviour of the "Labeler" |
| 25 | +#labelerFlags: |
| 26 | +# # If this flag is changed to 'false', labels would only be added when the PR is first created and not when existing |
| 27 | +# # PR is updated. |
| 28 | +# # The default is 'true' which means the labels would be added when PR is updated even if they were removed by the user |
| 29 | +# labelOnPRUpdates: true |
| 30 | + |
| 31 | +##### Reviewer ######################################################################################################### |
| 32 | +# Enable "Reviewer" for your PR that would add reviewers to PRs based on the labels that exist on the PR. |
| 33 | +# You have the option to set a default reviewer that gets added to every PR, or you can omit that config variable to skip it. |
| 34 | +addReviewerBasedOnLabel: |
| 35 | + # add list of reviewers to add by default to all PRs |
| 36 | + defaultReviewers: |
| 37 | + - stevepiercy |
| 38 | + # specify PR labels that you want to auto assign reviewers based on |
| 39 | +# labels: |
| 40 | +# label1: |
| 41 | +# - tyler-mairose-sp |
| 42 | +# - jordan-violet-sp |
| 43 | +# label2: |
| 44 | +# - kaxil |
| 45 | + |
| 46 | +##### Greetings ######################################################################################################## |
| 47 | +# Comment to be posted to welcome users when they open their first PR |
| 48 | +firstPRWelcomeComment: > |
| 49 | + Thanks for submitting your first pull request! You are awesome! :hugs: |
| 50 | +
|
| 51 | + <br>If you haven't done so already, read |
| 52 | + [Plone's Code of Conduct](https://plone.org/foundation/about/materials/foundation-resolutions/code-of-conduct) |
| 53 | + and [Contribute to documentation](https://6.docs.plone.org/contributing/documentation/index.html), |
| 54 | + as this will greatly help the review process. |
| 55 | +
|
| 56 | + <br>Welcome to the Plone community! :tada: |
| 57 | +
|
| 58 | +# Comment to be posted to congratulate user on their first merged PR |
| 59 | +firstPRMergeComment: > |
| 60 | + Congratulations on your first merged pull request in this project! :tada: |
| 61 | +
|
| 62 | +  |
| 63 | +
|
| 64 | + <br>Thank you for contributing, we are very proud of you! :heart: |
| 65 | +
|
| 66 | +# Comment to be posted to on first time issues |
| 67 | +firstIssueWelcomeComment: > |
| 68 | + Thanks for opening your first issue here! |
| 69 | + Your engagement is essential for open source projects, including Plone. :hugs: |
| 70 | +
|
| 71 | + <br>If you haven't done so already, |
| 72 | + read [Plone's Code of Conduct](https://plone.org/foundation/about/materials/foundation-resolutions/code-of-conduct). |
| 73 | + Also please follow the issue template, as it helps both you and other community members contribute more effectively. |
| 74 | + |
| 75 | + <br>If your issue is a feature request, others may raise its prominence through |
| 76 | + [feature voting](https://github.com/plone/documentation/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc%20). |
| 77 | +
|
| 78 | + <br>Welcome to the Plone community! :tada: |
| 79 | +
|
| 80 | +###### IssueLink Adder ################################################################################################# |
| 81 | +# Insert Issue (Jira/Github etc) link in PR description based on the Issue ID in PR title. |
| 82 | +#insertIssueLinkInPrDescription: |
| 83 | +# # specify the placeholder for the issue link that should be present in the description |
| 84 | +# descriptionIssuePlaceholderRegexp: "^Issue link: (.*)$" |
| 85 | +# matchers: |
| 86 | +# # you can have several matches - for different types of issues |
| 87 | +# # only the first matching entry is replaced |
| 88 | +# jiraIssueMatch: |
| 89 | +# # specify the regexp of issue id that you can find in the title of the PR |
| 90 | +# # the match groups can be used to build the issue id (${1}, ${2}, etc.). |
| 91 | +# titleIssueIdRegexp: \[(AIRFLOW-[0-9]{4})\] |
| 92 | +# # the issue link to be added. ${1}, ${2} ... are replaced with the match groups from the |
| 93 | +# # title match (remember to use quotes) |
| 94 | +# descriptionIssueLink: "[${1}](https://issues.apache.org/jira/browse/${1}/)" |
| 95 | +# docOnlyIssueMatch: |
| 96 | +# titleIssueIdRegexp: \[(AIRFLOW-X{4})\] |
| 97 | +# descriptionIssueLink: "`Document only change, no JIRA issue`" |
| 98 | +# |
| 99 | +###### Title Validator ################################################################################################# |
| 100 | +# Verifies if commit/PR titles match the regexp specified |
| 101 | +#verifyTitles: |
| 102 | +# # Regular expression that should be matched by titles of commits or PR |
| 103 | +# titleRegexp: ^\[AIRFLOW-[0-9]{4}\].*$|^\[AIRFLOW-XXXX\].*$ |
| 104 | +# # If set to true, it will always check the PR title (as opposed to the individual commits). |
| 105 | +# alwaysUsePrTitle: true |
| 106 | +# # If set to true, it will only check the commit in case there is a single commit. |
| 107 | +# # In case of multiple commits it will check PR title. |
| 108 | +# # This reflects the standard behaviour of Github that for `Squash & Merge` GitHub |
| 109 | +# # uses the PR title rather than commit messages for the squashed commit ¯\_(ツ)_/¯ |
| 110 | +# # For single-commit PRs it takes the squashed commit message from the commit as expected. |
| 111 | +# # |
| 112 | +# # If set to false it will check all commit messages. This is useful when you do not squash commits at merge. |
| 113 | +# validateEitherPrOrSingleCommitTitle: true |
| 114 | +# # The title the GitHub status should appear from. |
| 115 | +# statusTitle: "Title Validator" |
| 116 | +# # A custom message to be displayed when the title passes validation. |
| 117 | +# successMessage: "Validation successful!" |
| 118 | +# # A custom message to be displayed when the title fails validation. |
| 119 | +# # Allows insertion of ${type} (commit/PR), ${title} (the title validated) and ${regex} (the titleRegexp above). |
| 120 | +# failureMessage: "Wrong ${type} title: ${title}" |
| 121 | +# |
| 122 | +###### PR/Branch Up-To-Date Checker #################################################################################### |
| 123 | +## Check if the branch is up to date with master when certain files are modified |
| 124 | +#checkUpToDate: |
| 125 | +# # The default branch is "master", change the branch if you want to check against a different target branch |
| 126 | +# targetBranch: master |
| 127 | +# files: |
| 128 | +# # File paths that you want to check for |
| 129 | +# # In this example, it checks if the branch is up to date when alembic migrations are modified in the PR. |
| 130 | +# # It helps avoid multiple heads in alembic migrations in a collaborative development project. |
| 131 | +# - airflow/migrations/* |
| 132 | +# - airflow/migrations/**/* |
| 133 | +# - airflow/alembic.ini |
0 commit comments