forked from aws-powertools/powertools-lambda-python
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathboring-cyborg.yml
160 lines (148 loc) · 6.32 KB
/
boring-cyborg.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
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
##### Labeler ##########################################################################################################
labelPRBasedOnFilePath:
logger:
- aws_lambda_powertools/logging/*
- aws_lambda_powertools/logging/**/*
- aws_lambda_powertools/package_logger.py
tracer:
- aws_lambda_powertools/tracing/*
- aws_lambda_powertools/tracing/**/*
metrics:
- aws_lambda_powertools/metrics/*
- aws_lambda_powertools/metrics/**/*
event_handlers:
- aws_lambda_powertools/event_handler/*
- aws_lambda_powertools/event_handler/**/*
middleware_factory:
- aws_lambda_powertools/middleware_factory/*
- aws_lambda_powertools/middleware_factory/**/*
parameters:
- aws_lambda_powertools/parameters/*
- aws_lambda_powertools/parameters/**/*
batch:
- aws_lambda_powertools/batch/*
- aws_lambda_powertools/batch/**/*
validator:
- aws_lambda_powertools/validation/*
- aws_lambda_powertools/validation/**/*
event_sources:
- aws_lambda_powertools/data_classes/*
- aws_lambda_powertools/data_classes/**/*
parser:
- aws_lambda_powertools/parser/*
- aws_lambda_powertools/parser/**/*
idempotency:
- aws_lambda_powertools/idempotency/*
- aws_lambda_powertools/idempotency/**/*
feature_flags:
- aws_lambda_powertools/feature_flags/*
- aws_lambda_powertools/feature_flags/**/*
jmespath_util:
- aws_lambda_powertools/utilities/jmespath_utils/*
typing:
- aws_lambda_powertools/utilities/typing/*
- mypy.ini
utilities:
- aws_lambda_powertools/utilities/*
- aws_lambda_powertools/utilities/**/*
documentation:
- docs/*
- docs/**/*
- mkdocs.yml
github-actions:
- .github/workflows/*
- .github/workflows/**/*
- .github/dependabot.yml
- .github/boring-cyborg.yml
- .github/release-drafter.yml
- .github/semantic.yml
- .github/stale.yml
- .github/mergify.yml
github-templates:
- .github/ISSUE_TEMPLATE/*
- .github/PULL_REQUEST_TEMPLATE.md
- .github/.chglog/*
- .github/.chglog/**/*
internal:
- .flake8
- .bandit.baseline
- .gitignore
- .pre-commit-config.yaml
- MANIFEST.in
- Makefile
- CONTRIBUTING.md
- MAINTAINERS.md
- CODE_OF_CONDUCT.md
- LICENSE
- THIRD-PARTY-LICENSES
- aws_lambda_powertools_python/shared/*
- aws_lambda_powertools_python/shared/**
dependencies:
- pyproject.toml
- poetry.lock
tests:
- tests/*
- tests/**/*
- benchmark/*
- benchmark/**/*
##### Greetings ########################################################################################################
firstPRWelcomeComment: >
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
# Comment to be posted to congratulate user on their first merged PR
firstPRMergeComment: >
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!
# Comment to be posted to on first time issues
firstIssueWelcomeComment: >
Thanks for opening your first issue here! We'll come back to you as soon as we can.
###### IssueLink Adder #################################################################################################
# Insert Issue (Jira/Github etc) link in PR description based on the Issue ID in PR title.
#insertIssueLinkInPrDescription:
# # specify the placeholder for the issue link that should be present in the description
# descriptionIssuePlaceholderRegexp: "^Issue link: (.*)$"
# matchers:
# # you can have several matches - for different types of issues
# # only the first matching entry is replaced
# jiraIssueMatch:
# # specify the regexp of issue id that you can find in the title of the PR
# # the match groups can be used to build the issue id (${1}, ${2}, etc.).
# titleIssueIdRegexp: \[(AIRFLOW-[0-9]{4})\]
# # the issue link to be added. ${1}, ${2} ... are replaced with the match groups from the
# # title match (remember to use quotes)
# descriptionIssueLink: "[${1}](https://issues.apache.org/jira/browse/${1}/)"
# docOnlyIssueMatch:
# titleIssueIdRegexp: \[(AIRFLOW-X{4})\]
# descriptionIssueLink: "`Document only change, no JIRA issue`"
###### 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: ^\[AIRFLOW-[0-9]{4}\].*$|^\[AIRFLOW-XXXX\].*$
# # 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}"
###### PR/Branch Up-To-Date Checker ####################################################################################
# Check if the branch is up to date with develop when certain files are modified
#checkUpToDate:
# # The default branch is "develop", change the branch if you want to check against a different target branch
# targetBranch: develop
# files:
# # File paths that you want to check for
# # In this example, it checks if the branch is up to date when alembic migrations are modified in the PR.
# # It helps avoid multiple heads in alembic migrations in a collaborative development project.
# - airflow/migrations/*
# - airflow/migrations/**/*
# - airflow/alembic.ini