mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-12-15 02:41:59 +00:00
43 lines
1.5 KiB
Markdown
43 lines
1.5 KiB
Markdown
<!---
|
|
A technical comment, you are free to remove or leave it as it is when PR is created
|
|
The following categories are used in the next scripts, update them accordingly
|
|
utils/changelog/changelog.py
|
|
tests/ci/cancel_and_rerun_workflow_lambda/app.py
|
|
-->
|
|
### Changelog category (leave one):
|
|
- New Feature
|
|
- Improvement
|
|
- Performance Improvement
|
|
- Backward Incompatible Change
|
|
- Build/Testing/Packaging Improvement
|
|
- Documentation (changelog entry is not required)
|
|
- Bug Fix (user-visible misbehavior in an official stable release)
|
|
- CI Fix or Improvement (changelog entry is not required)
|
|
- Not for changelog (changelog entry is not required)
|
|
|
|
|
|
### Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
|
|
...
|
|
|
|
### Documentation entry for user-facing changes
|
|
|
|
- [ ] Documentation is written (mandatory for new features)
|
|
|
|
<!---
|
|
Directly edit documentation source files in the "docs" folder with the same pull-request as code changes
|
|
|
|
or
|
|
|
|
Add a user-readable short description of the changes that should be added to docs.clickhouse.com below.
|
|
|
|
At a minimum, the following information should be added (but add more as needed).
|
|
- Motivation: Why is this function, table engine, etc. useful to ClickHouse users?
|
|
|
|
- Parameters: If the feature being added takes arguments, options or is influenced by settings, please list them below with a brief explanation.
|
|
|
|
- Example use: A query or command.
|
|
-->
|
|
|
|
|
|
> Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/
|