@@ -186,80 +186,8 @@ to ask for a review, please reach out to the project leads.
186
186
187
187
### Pull request template
188
188
189
- The following pull request template will be successively added to all
189
+ The [ pull request] [ pull_request ] template will be successively added to all
190
190
repositories. Until that is the case, you can already make use of it by
191
191
self-reviewing your pull requests according to the checklist and descriptions.
192
192
193
- #### Description
194
-
195
- > Please include a summary of the change and the relevant issue(s) it resolves,
196
- > if any (otherwise delete that line), e.g., ` Fixes #123 ` . If the PR addresses
197
- > more than one issue, please add multiple lines, each starting with 'Fixes #'.
198
- > Please stick to that syntax precisely, including whitespaces, otherwise the
199
- > issue(s) may not be linked to the PR.
200
- >
201
- > In the summary, list any dependencies that are required for this change.
202
- > Please use bullet points for the description. Please also briefly describe
203
- > the relevant motivation and context briefly. For very trivial changes that are
204
- > duly explained by the PR title, a description can be omitted.
205
-
206
- -
207
-
208
- Fixes #(issue number)
209
-
210
- #### Checklist
211
-
212
- > Please go through the following checklist to ensure that your change is ready
213
- > for review. Please do not forget to double check the list after you have
214
- > modified your PR, e.g., if you have added commits to address reviewer
215
- > comments or to fix failing automated checks. ** Please check items also if they
216
- > do not apply to your change** , e.g., if your change does not require an update
217
- > of the user-facing documentation, still check the box.
218
- >
219
- > Generally, ** PRs are only reviewed when all boxes are ticked off and all
220
- > automated checks pass** (use the comment section below if you believe that
221
- > your PR is ready to be merged even though not all boxes were ticked off).
222
-
223
- - [ ] My code follows the [ contributing guidelines] ( workflow.md ) of this
224
- project, including, in particular, with regard to any style guidelines
225
- - [ ] The title of my PR complies with the [ Conventional Commits
226
- specification] [ conv-commits ] ; in particular, it clearly indicates
227
- that a change is a breaking change
228
- - [ ] I acknowledge that all my commits will be squashed into a single commit,
229
- using the PR title as the commit message
230
- - [ ] I have performed a self-review of my own code
231
- - [ ] I have commented my code in hard-to-understand areas
232
- - [ ] I have updated the user-facing documentation to describe any new or
233
- changed behavior
234
- - [ ] I have added type annotations for all function/class/method interfaces
235
- or updated existing ones (only for Python, TypeScript, etc.)
236
- - [ ] I have provided appropriate documentation (e.g., [ Google-style
237
- Python docstrings] [ py-doc-google ] or [ JSDoc block tags] [ jsdoc ] ) for all
238
- packages/modules/functions/classes/methods or updated existing ones
239
- - [ ] My changes generate no new warnings
240
- - [ ] I have added tests that prove my fix is effective or that my feature
241
- works
242
- - [ ] New and existing unit tests pass locally with my changes
243
- - [ ] I have not reduced the existing code coverage
244
- - [ ] I have asked the [ @all-contributors bot] [ all-contributors-bot ] to
245
- acknowledge my contributions by commenting on this PR with a request of
246
- the form `@all-contributors please add @YOUR_GH_HANDLE for TYPE_1,
247
- TYPE_2, ...` , where ` TYPE_1` etc. refer to [ contribution types supported
248
- by the All Contributors Specification] [ all-contributors-types ] OR I do
249
- not want my contributions to be acknowledged by [ All
250
- Contributors] [ all-contributors ]
251
-
252
- !!! note "All Contributors"
253
-
254
- The [All Contributors][all-contributors] bot may not be available in all
255
- repositories yet. In that case, please ignore the last bullet point.
256
-
257
- #### Comments
258
-
259
- > If there are unchecked boxes in the list above, but you would still like your
260
- > PR to be reviewed or considered for merging, please describe here why boxes
261
- > were not checked. For example, if you are positive that your commits should
262
- > _ not_ be squased when merging, please explain why you think the PR warrants
263
- > or requires multiple commits to be added to the history (but note that in
264
- > that case, it is a prerequisite that all commits follow the Conventional
265
- > Commits specification).
193
+ [ pull_request ] : PULL_REQUEST_TEMPLATE.md
0 commit comments