This is an automated email from the ASF dual-hosted git repository.
luoyuxia pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fluss.git
The following commit(s) were added to refs/heads/main by this push:
new 9f0284ddc [docs] Add rust/python/c++/elixir component tags (#3602)
9f0284ddc is described below
commit 9f0284ddccef51ad417abf6fccadba4a0d33ea96
Author: Anton Borisov <[email protected]>
AuthorDate: Tue Jul 7 02:28:57 2026 +0100
[docs] Add rust/python/c++/elixir component tags (#3602)
---
.github/PULL_REQUEST_TEMPLATE.md | 2 +-
AGENTS.md | 2 +-
website/community/how-to-contribute/bug-reports-feature-requests.md | 2 +-
website/community/how-to-contribute/contribute-code.md | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 8f23449c8..b4afeb9d8 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -5,7 +5,7 @@
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos
in JavaDoc or documentation files, which need no issue.
- - Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
+ - Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink], [rust], [python], [c++],
[elixir]). Skip *[component]* if you are unsure about which is the best
component.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
diff --git a/AGENTS.md b/AGENTS.md
index 87708de46..6ac444a36 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -431,7 +431,7 @@ git remote add fork
https://github.com/<your-username>/fluss.git
Detailed explanation of changes and motivation.
```
-**Component tags:** `[client]`, `[server]`, `[rpc]`, `[flink]`, `[spark]`,
`[docs]`, `[build]`, `[test]`
+**Component tags:** `[client]`, `[server]`, `[rpc]`, `[flink]`, `[spark]`,
`[rust]`, `[python]`, `[c++]`, `[elixir]`, `[docs]`, `[build]`, `[test]`
### Pre-Push Self-Review
diff --git
a/website/community/how-to-contribute/bug-reports-feature-requests.md
b/website/community/how-to-contribute/bug-reports-feature-requests.md
index 7363b76a8..185256c53 100644
--- a/website/community/how-to-contribute/bug-reports-feature-requests.md
+++ b/website/community/how-to-contribute/bug-reports-feature-requests.md
@@ -13,7 +13,7 @@ Considerations before opening an issue:
- Make sure that the issue corresponds to a genuine bug or enhancement
request. Exceptions are made for typos in documentation files, which can be
reported directly.
-- Provide a clear and descriptive title. Use component labels (such as
`component=server`, `component=client`, `component=connector`,
`component=docs`) to help categorize your issue and make it easier to filter
and search.
+- Provide a clear and descriptive title. Use component labels (such as
`component=server`, `component=client`, `component=connector`,
`component=rust`, `component=docs`) to help categorize your issue and make it
easier to filter and search.
- Fill out the issue template to describe the problem or enhancement clearly.
Please describe it such that maintainers understand the context and impact from
the description, not only from reproduction steps.
diff --git a/website/community/how-to-contribute/contribute-code.md
b/website/community/how-to-contribute/contribute-code.md
index 31ac2418f..6e0c115c5 100644
--- a/website/community/how-to-contribute/contribute-code.md
+++ b/website/community/how-to-contribute/contribute-code.md
@@ -50,7 +50,7 @@ Considerations before opening a pull request:
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos
in JavaDoc or documentation files, which need no issue.
-- Name the pull request in the format "[component] Title of the pull request",
where *[component]* should be replaced by the name of the component being
changed. Typically, this corresponds to the component label assigned to the
issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component. **Hotfixes** should be named for
example `[hotfix][docs] Expand JavaDoc for PunctuatedWatermarkGenerator`.
+- Name the pull request in the format "[component] Title of the pull request",
where *[component]* should be replaced by the name of the component being
changed. Typically, this corresponds to the component label assigned to the
issue (e.g., [kv], [log], [client], [flink], [rust], [python], [c++],
[elixir]). Skip *[component]* if you are unsure about which is the best
component. **Hotfixes** should be named for example `[hotfix][docs] Expand
JavaDoc for PunctuatedWatermarkGenerator`.
- Fill out the pull request template to describe the changes contributed by
the pull request. Please describe it such that the reviewer understands the
problem and solution from the description, not only from the code. That will
give reviewers the context they need to do the review.
