This is an automated email from the ASF dual-hosted git repository.
tomsun28 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git
The following commit(s) were added to refs/heads/master by this push:
new 42f2365e29 [fix] fix the dead link issue in ci (#4148)
42f2365e29 is described below
commit 42f2365e29b235dc11f4391762477d83986f148f
Author: Duansg <[email protected]>
AuthorDate: Thu May 28 23:23:59 2026 +0800
[fix] fix the dead link issue in ci (#4148)
---
CONTRIBUTING.md | 136 ++++++++++-----------
home/docs/community/contribution.md | 14 +--
.../current/community/contribution.md | 16 +--
3 files changed, 83 insertions(+), 83 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9f32988357..b749f2c357 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,10 +1,10 @@
-## Contributor Guide [中文贡献者指南](#贡献者指南)
+## Contributor Guide [中文贡献者指南](#贡献者指南)
-> We are committed to maintaining a happy community that helps each other,
welcome every contributor to join us!
+> We are committed to maintaining a happy community that helps each other,
welcome every contributor to join us!
-### Kinds of Contributions
+### Kinds of Contributions
-> In the HertzBeat community, there are many ways to contribute:
+> In the HertzBeat community, there are many ways to contribute:
- 💻**Code**: Can help the community complete some tasks, write new features or
fix some bugs;
@@ -20,14 +20,14 @@
- 💬**Suggestion**: You can also make some suggestions to the project or
community to promote the healthy development of the community;
-More see [Contribution Types](https://allcontributors.org/emoji-key)
+More see [Contribution
Types](https://allcontributors.org/en/reference/emoji-key/)
-Even small corrections to typos are very welcome :)
+Even small corrections to typos are very welcome :)
-### Getting HertzBeat up and running
+### Getting HertzBeat up and running
> To get HertzBeat code running on your development tools, and able to debug
> with breakpoints.
-> This is a front-end and back-end separation project. To start the local
code, the back-end [startup](hertzbeat-startup) and the front-end
[web-app](web-app) must be started separately.
+> This is a front-end and back-end separation project. To start the local
code, the back-end [startup](hertzbeat-startup) and the front-end
[web-app](web-app) must be started separately.
#### Backend start
@@ -57,51 +57,51 @@ Even small corrections to typos are very welcome :)
6. Browser access to localhost:4200 to start, default account/password is
*admin/hertzbeat*
-### Find tasks
+### Find tasks
-Find the issue you are interested in! On our GitHub repo issue list, we often
publish some issues with the label good first issue or status: volunteer
wanted.
-These issues welcome the help of contributors. Among them, good first issues
tend to have low thresholds and are suitable for novices.
+Find the issue you are interested in! On our GitHub repo issue list, we often
publish some issues with the label good first issue or status: volunteer wanted.
+These issues welcome the help of contributors. Among them, good first issues
tend to have low thresholds and are suitable for novices.
-Of course, if you have a good idea, you can also propose it directly on GitHub
Discussion or contact with community.
+Of course, if you have a good idea, you can also propose it directly on GitHub
Discussion or contact with community.
-### Submit Pull Request
+### Submit Pull Request
-1. First you need to fork your target [hertzbeat
repository](https://github.com/apache/hertzbeat).
+1. First you need to fork your target [hertzbeat
repository](https://github.com/apache/hertzbeat).
2. Then download the code locally with git command:
```shell
- git clone [email protected]:${YOUR_USERNAME}/hertzbeat.git #Recommended
+ git clone [email protected]:${YOUR_USERNAME}/hertzbeat.git #Recommended
```
-3. After the download is complete, please refer to the getting started guide
or README file of the target repository to initialize the project.
+3. After the download is complete, please refer to the getting started guide
or README file of the target repository to initialize the project.
4. Then, you can refer to the following command to submit the code:
```shell
- git checkout -b a-feature-branch #Recommended
+ git checkout -b a-feature-branch #Recommended
```
-5. Submit the coed as a commit, the commit message format specification
required: [module name or type name]feature or bugfix or doc: custom message.
+5. Submit the coed as a commit, the commit message format specification
required: [module name or type name]feature or bugfix or doc: custom message.
```shell
- git add <modified file/path>
- git commit -m '[docs]feature: necessary instructions' #Recommended
+ git add <modified file/path>
+ git commit -m '[docs]feature: necessary instructions' #Recommended
```
-6. Push to the remote repository
+6. Push to the remote repository
```shell
- git push origin a-feature-branch
+ git push origin a-feature-branch
```
-7. Then you can initiate a new PR (Pull Request) on GitHub.
+7. Then you can initiate a new PR (Pull Request) on GitHub.
-Please note that the title of the PR needs to conform to our spec, and write
the necessary description in the PR to facilitate code review by Committers and
other contributors.
+Please note that the title of the PR needs to conform to our spec, and write
the necessary description in the PR to facilitate code review by Committers and
other contributors.
-### Wait for the code to be merged
+### Wait for the code to be merged
-After submitting the PR, the Committee or the community's friends will review
the code you submitted (Code Review), and will propose some modification
suggestions or conduct some discussions. Please pay attention to your PR in
time.
+After submitting the PR, the Committee or the community's friends will review
the code you submitted (Code Review), and will propose some modification
suggestions or conduct some discussions. Please pay attention to your PR in
time.
-If subsequent changes are required, there is no need to initiate a new PR.
After submitting a commit on the original branch and pushing it to the remote
repository, the PR will be automatically updated.
+If subsequent changes are required, there is no need to initiate a new PR.
After submitting a commit on the original branch and pushing it to the remote
repository, the PR will be automatically updated.
-In addition, our project has a relatively standardized and strict CI
inspection process. After submitting PR, CI will be triggered. Please pay
attention to whether it passes the CI inspection.
+In addition, our project has a relatively standardized and strict CI
inspection process. After submitting PR, CI will be triggered. Please pay
attention to whether it passes the CI inspection.
-Finally, the Committers can merge the PR into the master branch.
+Finally, the Committers can merge the PR into the master branch.
-### After the code is merged
+### After the code is merged
-After the code has been merged, you can delete the development branch on both
the local and remote repositories:
+After the code has been merged, you can delete the development branch on both
the local and remote repositories:
```shell
git branch -d a-dev-branch
@@ -112,18 +112,18 @@ On the master/main branch, you can do the following to
sync the upstream reposit
```shell
git remote add upstream https://github.com/apache/hertzbeat.git #Bind the
remote warehouse, if it has been executed, it does not need to be executed again
-git checkout master
+git checkout master
git pull upstream master
```
### HertzBeat Improvement Proposal (HIP)
If you have major new features(e.g., support metrics push gateway, support
logs monitoring), you need to write a design document known as a HertzBeat
Improvement Proposal (HIP). Before starting to write a HIP, make sure you
follow the process [here](https://github.com/apache/hertzbeat/tree/master/hip).
-### How to become a Committer?
+### How to become a Committer?
-With the above steps, you are a contributor to HertzBeat. Repeat the previous
steps to stay active in the community, keep at, you can become a Committer!
+With the above steps, you are a contributor to HertzBeat. Repeat the previous
steps to stay active in the community, keep at, you can become a Committer!
-### Join Discussion
+### Join Discussion
[Join the Mailing
Lists](https://lists.apache.org/[email protected]) : Mail to
`[email protected]` to subscribe mailing lists.
@@ -133,19 +133,19 @@ Add WeChat account `ahertzbeat` to pull you into the
WeChat group.
-<br>
+<br>
------
<br>
-## 贡献者指南
+## 贡献者指南
-> 非常欢迎参与项目贡献，我们致力于维护一个互相帮助的快乐社区。
+> 非常欢迎参与项目贡献，我们致力于维护一个互相帮助的快乐社区。
-### 贡献方式
+### 贡献方式
-> 在 HertzBeat 社区，贡献方式有很多:
+> 在 HertzBeat 社区，贡献方式有很多:
- 💻**代码**：可以帮助社区完成一些任务、编写新的feature或者是修复一些bug；
@@ -159,15 +159,15 @@ Add WeChat account `ahertzbeat` to pull you into the
WeChat group.
- 💡**布道**：可以帮助宣传或推广 HertzBeat 社区，在 meetup 或 summit 中演讲；
-- 💬**建议**：也可以对项目或者社区提出一些建议，促进社区的良性发展；
+- 💬**建议**：也可以对项目或者社区提出一些建议，促进社区的良性发展；
-更多贡献方式参见 [Contribution Types](https://allcontributors.org/emoji-key)
+更多贡献方式参见 [Contribution
Types](https://allcontributors.org/en/reference/emoji-key/)
-即便是小到错别字的修正我们也都非常欢迎 :)
+即便是小到错别字的修正我们也都非常欢迎 :)
-### 让 HertzBeat 运行起来
+### 让 HertzBeat 运行起来
-> 让 HertzBeat 的代码在您的开发工具上运行起来，并且能够断点调试。
+> 让 HertzBeat 的代码在您的开发工具上运行起来，并且能够断点调试。
> 此为前后端分离项目，本地代码启动需将后端[hertzbeat-startup](hertzbeat-startup)和前端[web-app](web-app)分别启动生效。
#### 后端启动
@@ -197,71 +197,71 @@ Add WeChat account `ahertzbeat` to pull you into the
WeChat group.
6. 浏览器访问 localhost:4200 即可开始，默认账号密码 *admin/hertzbeat*
-### 寻找任务
+### 寻找任务
寻找您感兴趣的Issue！在我们的GitHub仓库和邮件列表中，我们经常会发布一些带有 good first issue 或者 status:
volunteer wanted 标签的issue，这些issue都欢迎贡献者的帮助。
-其中good first issue往往门槛较低、适合新手。
+其中good first issue往往门槛较低、适合新手。
-当然，如果您有好的想法，也可以直接在GitHub Discussion 中提出或者联系社区。
+当然，如果您有好的想法，也可以直接在GitHub Discussion 中提出或者联系社区。
### 提交 Pull Request
1. 首先您需要 Fork 目标仓库 [hertzbeat repository](https://github.com/apache/hertzbeat).
-2. 然后 用git命令 将代码下载到本地:
+2. 然后 用git命令 将代码下载到本地:
```shell
- git clone [email protected]:${YOUR_USERNAME}/hertzbeat.git #Recommended
+ git clone [email protected]:${YOUR_USERNAME}/hertzbeat.git #Recommended
```
3. 下载完成后，请参考目标仓库的入门指南或者 README 文件对项目进行初始化。
-4. 接着，您可以参考如下命令进行代码的提交, 切换新的分支, 进行开发:
+4. 接着，您可以参考如下命令进行代码的提交, 切换新的分支, 进行开发:
```shell
- git checkout -b a-feature-branch #Recommended
+ git checkout -b a-feature-branch #Recommended
```
-5. 提交 commit , commit 描述信息需要符合约定格式: [module name or type name]feature or
bugfix or doc: custom message.
+5. 提交 commit , commit 描述信息需要符合约定格式: [module name or type name]feature or
bugfix or doc: custom message.
```shell
- git add <modified file/path>
- git commit -m '[docs]feature: necessary instructions' #Recommended
+ git add <modified file/path>
+ git commit -m '[docs]feature: necessary instructions' #Recommended
```
-6. 推送到远程仓库
+6. 推送到远程仓库
```shell
- git push origin a-feature-branch
+ git push origin a-feature-branch
```
7. 然后您就可以在 GitHub 上发起新的 PR (Pull Request)。
-请注意 PR 的标题需要符合我们的规范，并且在 PR 中写上必要的说明，来方便 Committer 和其他贡献者进行代码审查。
+请注意 PR 的标题需要符合我们的规范，并且在 PR 中写上必要的说明，来方便 Committer 和其他贡献者进行代码审查。
-### 等待PR代码被合并
+### 等待PR代码被合并
-在提交了 PR 后，Committer 或者社区的小伙伴们会对您提交的代码进行审查（Code
Review），会提出一些修改建议，或者是进行一些讨论，请及时关注您的PR。
+在提交了 PR 后，Committer 或者社区的小伙伴们会对您提交的代码进行审查（Code
Review），会提出一些修改建议，或者是进行一些讨论，请及时关注您的PR。
若后续需要改动，不需要发起一个新的 PR，在原有的分支上提交 commit 并推送到远程仓库后，PR会自动更新。
另外，我们的项目有比较规范和严格的 CI 检查流程，在提交 PR 之后会触发 CI，请注意是否通过 CI 检查。
-最后，Committer 可以将 PR 合并入 master 主分支。
+最后，Committer 可以将 PR 合并入 master 主分支。
-### 代码被合并后
+### 代码被合并后
-在代码被合并后，您就可以在本地和远程仓库删除这个开发分支了：
+在代码被合并后，您就可以在本地和远程仓库删除这个开发分支了：
```shell
git branch -d a-dev-branch
git push origin --delete a-dev-branch
```
-在主分支上，您可以执行以下操作来同步上游仓库：
+在主分支上，您可以执行以下操作来同步上游仓库：
```shell
git remote add upstream https://github.com/apache/hertzbeat.git #Bind the
remote warehouse, if it has been executed, it does not need to be executed again
-git checkout master
+git checkout master
git pull upstream master
```
### HertzBeat 改进提案 (HIP)
如果您有重大的新特性（例如，支持指标推送网关，日志监控等），您需要编写一个被称为 HertzBeat 改进提案（HertzBeat Improvement
Proposal，HIP）的设计文档。在开始编写 HIP
之前，请确保您遵循了[这里](https://github.com/apache/hertzbeat/tree/master/hip)的流程。
-### 如何成为Committer？
+### 如何成为Committer？
-通过上述步骤，您就是 HertzBeat 的贡献者了。重复前面的步骤，在社区中保持活跃，坚持下去，您就能成为 Committer！
+通过上述步骤，您就是 HertzBeat 的贡献者了。重复前面的步骤，在社区中保持活跃，坚持下去，您就能成为 Committer！
### 加入讨论交流
@@ -271,4 +271,4 @@ Add WeChat account `ahertzbeat` to pull you into the WeChat
group.
### 模块
-
+
diff --git a/home/docs/community/contribution.md
b/home/docs/community/contribution.md
index 73f25ca242..59e861a10c 100644
--- a/home/docs/community/contribution.md
+++ b/home/docs/community/contribution.md
@@ -41,7 +41,7 @@ limitations under the License.
- 💬**Suggestion**: You can also make some suggestions to the project or
community to promote the healthy development of the community;
-More see [Contribution Types](https://allcontributors.org/emoji-key)
+More see [Contribution
Types](https://allcontributors.org/en/reference/emoji-key/)
Even small corrections to typos are very welcome :)
@@ -85,27 +85,27 @@ Of course, if you have a good idea, you can also propose it
directly on GitHub D
2. Then download the code locally with git command:
```shell
- git clone [email protected]:`YOUR_USERNAME`/hertzbeat.git #Recommended
+ git clone [email protected]:`YOUR_USERNAME`/hertzbeat.git #Recommended
```
3. After the download is complete, please refer to the getting started guide
or README file of the target repository to initialize the project.
4. Then, you can refer to the following command to submit the code:
```shell
- git checkout -b a-feature-branch #Recommended
+ git checkout -b a-feature-branch #Recommended
```
5. Submit the coed as a commit, the commit message format specification
required: [module name or type name]feature or bugfix or doc: custom message.
```shell
- git add <modified file/path>
- git commit -m '[docs]feature: necessary instructions' #Recommended
+ git add <modified file/path>
+ git commit -m '[docs]feature: necessary instructions' #Recommended
```
6. Push to the remote repository
```shell
- git push origin a-feature-branch
+ git push origin a-feature-branch
```
7. Then you can initiate a new PR (Pull Request) on GitHub.
@@ -135,7 +135,7 @@ On the master/main branch, you can do the following to sync
the upstream reposit
```shell
git remote add upstream https://github.com/apache/hertzbeat.git #Bind the
remote warehouse, if it has been executed, it does not need to be executed again
-git checkout master
+git checkout master
git pull upstream master
```
diff --git
a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/contribution.md
b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/contribution.md
index b3a92a6599..2a5ec4a44c 100644
---
a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/contribution.md
+++
b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/contribution.md
@@ -1,5 +1,5 @@
---
-id: contribution
+id: contribution
title: 贡献指南
sidebar_position: 0
---
@@ -41,7 +41,7 @@ limitations under the License.
- 💬**建议**：也可以对项目或者社区提出一些建议，促进社区的良性发展；
-更多贡献方式参见 [Contribution Types](https://allcontributors.org/emoji-key)
+更多贡献方式参见 [Contribution
Types](https://allcontributors.org/en/reference/emoji-key/)
即便是小到错别字的修正我们也都非常欢迎 :)
@@ -89,27 +89,27 @@ limitations under the License.
2. 然后 用 git 命令 将代码下载到本地:
```shell
- git clone [email protected]:`YOUR_USERNAME`/hertzbeat.git #Recommended
+ git clone [email protected]:`YOUR_USERNAME`/hertzbeat.git #Recommended
```
3. 下载完成后，请参考目标仓库的入门指南或者 README 文件对项目进行初始化。
4. 接着，您可以参考如下命令进行代码的提交, 切换新的分支, 进行开发:
```shell
- git checkout -b a-feature-branch #Recommended
+ git checkout -b a-feature-branch #Recommended
```
5. 提交 commit, commit 描述信息需要符合约定格式: [module name or type name]feature or bugfix
or doc: custom message.
```shell
- git add <modified file/path>
- git commit -m '[docs]feature: necessary instructions' #Recommended
+ git add <modified file/path>
+ git commit -m '[docs]feature: necessary instructions' #Recommended
```
6. 推送到远程仓库
```shell
- git push origin a-feature-branch
+ git push origin a-feature-branch
```
7. 然后您就可以在 GitHub 上发起新的 PR (Pull Request)。
@@ -139,7 +139,7 @@ git push origin --delete a-dev-branch
```shell
git remote add upstream https://github.com/apache/hertzbeat.git #Bind the
remote warehouse, if it has been executed, it does not need to be executed again
-git checkout master
+git checkout master
git pull upstream master
```
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
