This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 182257a916 Automated deployment:
3c1ca9301a648e2aa9ed11e718d630d098c7f6fc
182257a916 is described below
commit 182257a9165bd4bc76d90c8f63b8069e8c659680
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon May 11 06:17:58 2026 +0000
Automated deployment: 3c1ca9301a648e2aa9ed11e718d630d098c7f6fc
---
data/doc/en-us.json | 6 +-
data/doc/zh-cn.json | 6 +-
.../en-us/dev/contribute/join/commit-message.json | 287 +++++----------------
.../en-us/dev/contribute/join/pull-request.json | 2 +-
.../doc/en-us/dev/contribute/join/submit-code.json | 2 +-
.../zh-cn/dev/contribute/join/commit-message.json | 287 +++++----------------
.../zh-cn/dev/contribute/join/pull-request.json | 2 +-
.../doc/zh-cn/dev/contribute/join/submit-code.json | 2 +-
8 files changed, 138 insertions(+), 456 deletions(-)
diff --git a/data/doc/en-us.json b/data/doc/en-us.json
index 1b0aee9586..dfbee4e8ca 100644
--- a/data/doc/en-us.json
+++ b/data/doc/en-us.json
@@ -44583,7 +44583,7 @@
]
},
{
- "content": "Submit Code\n\n\nFirst from the remote repository
https://github.com/apache/dolphinscheduler.git fork a copy of the code into
your own repository\n\n\nThere are currently three branches in the remote
repository:\n\nmaster normal delivery branch\nAfter the stable
release, merge the code from the stable branch into the master.\ndev
daily development branch\nEvery day dev development branch, newly submitted
code can pull request to this branch.\n\n\n\n [...]
+ "content": "Submit Code\n\n\nFirst from the remote repository
https://github.com/apache/dolphinscheduler.git fork a copy of the code into
your own repository\n\n\nThere are currently three branches in the remote
repository:\n\nmaster normal delivery branch\nAfter the stable
release, merge the code from the stable branch into the master.\ndev
daily development branch\nEvery day dev development branch, newly submitted
code can pull request to this branch.\n\n\n\n [...]
"version": "dev",
"link": "/contribute/join/submit-code",
"title": "Submit Code",
@@ -44627,7 +44627,7 @@
]
},
{
- "content": "Pull Request Notice\nPreface\nPull Request is a way of
software cooperation, which is a process of bringing code involving different
functions into the trunk. During this process, the code can be discussed,
reviewed, and modified.\nIn Pull Request, we try not to discuss the
implementation of the code. The general implementation of the code and its
logic should be determined in Issue. In the Pull Request, we only focus on the
code format and code specification, so as to av [...]
+ "content": "Pull Request Notice\nPreface\nPull Request is a way of
software cooperation, which is a process of bringing code involving different
functions into the trunk. During this process, the code can be discussed,
reviewed, and modified.\nIn Pull Request, we try not to discuss the
implementation of the code. The general implementation of the code and its
logic should be determined in Issue. In the Pull Request, we only focus on the
code format and code specification, so as to av [...]
"version": "dev",
"link": "/contribute/join/pull-request",
"title": "Pull Request Notice",
@@ -44638,7 +44638,7 @@
]
},
{
- "content": "Commit Message Notice\nPreface\nA good commit message can help
other developers (or future developers) quickly understand the context of
related changes, and can also help project managers determine whether the
commit is suitable for inclusion in the release. But when we checked the commit
logs of many open source projects, we found an interesting problem. Some
developers have very good code quality, but the commit message record is rather
confusing. When other contributo [...]
+ "content": "Commit Message Notice\nA good commit message states what
changed and why at a glance. The full story belongs in the linked Issue / Pull
Request — keep the commit message itself
concise.\nFormat\n[Type-ISSUE_ID][Scope] Subject\n\n(optional body — bullet
list of the main changes)\n\n(optional footer — BREAKING CHANGE / Closes
#xxx)\n\nHeader is required; body and footer are optional. Aim for a Subject
under 72 characters so it does not get truncated on GitHub.\nType (requir [...]
"version": "dev",
"link": "/contribute/join/commit-message",
"title": "Commit Message Notice",
diff --git a/data/doc/zh-cn.json b/data/doc/zh-cn.json
index 54cabe3858..8fe32a7331 100644
--- a/data/doc/zh-cn.json
+++ b/data/doc/zh-cn.json
@@ -40095,7 +40095,7 @@
]
},
{
- "content":
"提交代码\n\n\n首先从远端仓库https://github.com/apache/dolphinscheduler.git
fork一份代码到自己的仓库中\n\n\n远端仓库中目前有三个分支：\n\n\nmaster
正常交付分支\n发布稳定版本以后，将稳定版本分支的代码合并到master上。\n\n\ndev
日常开发分支\n日常dev开发分支，新提交的代码都可以pull request到这个分支上。\n\n\nbranch-1.0.0
发布版本分支\n发布版本分支，后续会有2.0...等版本分支。\n\n\n\n\n把自己仓库clone到本地\n git clone
https://github.com/apache/dolphinscheduler.git\n\n\n添加远端仓库地址，命名为upstream\ngit
remote add upstream https://github.com/apache/dolphinscheduler.git\n\n\n查看仓库：\n
git remote -v\n\n\n\n此时会 [...]
+ "content":
"提交代码\n\n\n首先从远端仓库https://github.com/apache/dolphinscheduler.git
fork一份代码到自己的仓库中\n\n\n远端仓库中目前有三个分支：\n\n\nmaster
正常交付分支\n发布稳定版本以后，将稳定版本分支的代码合并到master上。\n\n\ndev
日常开发分支\n日常dev开发分支，新提交的代码都可以pull request到这个分支上。\n\n\nbranch-1.0.0
发布版本分支\n发布版本分支，后续会有2.0...等版本分支。\n\n\n\n\n把自己仓库clone到本地\n git clone
https://github.com/apache/dolphinscheduler.git\n\n\n添加远端仓库地址，命名为upstream\ngit
remote add upstream https://github.com/apache/dolphinscheduler.git\n\n\n查看仓库：\n
git remote -v\n\n\n\n此时会 [...]
"version": "dev",
"link": "/contribute/join/submit-code",
"title": "提交代码",
@@ -40139,7 +40139,7 @@
]
},
{
- "content": "Pull Request 须知\n前言\nPull Request
本质上是一种软件的合作方式，是将涉及不同功能的代码，纳入主干的一种流程。这个过程中，可以进行讨论、审核和修改代码。\n在 Pull Request
中尽量不讨论代码的实现方案，代码及其逻辑的大体实现方案应该尽量在\nIssue 或者邮件列表中被讨论确定，在 Pull Request
中我们尽量只关注代码的格式以及代码规范等信息，从而避免实现方式的意见不同而导致\nwaste time。\n规范\nPull Request
标题\n标题格式：[Pull Request 类型-Issue 号][模块名] Pull Request 描述\n其中Pull Request
类型和Issue 类型的对应关系如下：\n\n \n \n Issue 类型\n Pull
Request 类型\n 样例（假设 Issue 号为 3333）\n \n \n \n \n
[...]
+ "content": "Pull Request 须知\n前言\nPull Request
本质上是一种软件的合作方式，是将涉及不同功能的代码，纳入主干的一种流程。这个过程中，可以进行讨论、审核和修改代码。\n在 Pull Request
中尽量不讨论代码的实现方案，代码及其逻辑的大体实现方案应该尽量在\nIssue 或者邮件列表中被讨论确定，在 Pull Request
中我们尽量只关注代码的格式以及代码规范等信息，从而避免实现方式的意见不同而导致\nwaste time。\n规范\nPull Request
标题\n标题格式：[Pull Request 类型-Issue 号][模块名] Pull Request 描述\n其中Pull Request
类型和Issue 类型的对应关系如下：\n\n \n \n Issue 类型\n Pull
Request 类型\n 样例（假设 Issue 号为 3333）\n \n \n \n \n
[...]
"version": "dev",
"link": "/contribute/join/pull-request",
"title": "Pull Request 须知",
@@ -40150,7 +40150,7 @@
]
},
{
- "content": "Commit Message 须知\n前言\n一个好的 commit message
是能够帮助其他的开发者（或者未来的开发者）快速理解相关变更的上下文，同时也可以帮助项目管理人员确定该提交是否适合包含在发行版中。但当我们在查看了很多开源项目的
commit log 后，发现一个有趣的问题，一部分开发者，代码质量很不错，但是 commit message
记录却比较混乱，当其他贡献者或者学习者在查看代码的时候，并不能通过 commit log 很直观的了解\n该提交前后变更的目的，正如 Peter
Hutterer 所言：Re-establishing the context of a piece of code is wasteful. We
can’t avoid it completely, so our efforts should go to reducing it as much as
possible. Commit messages can do exactly that and as a result, a commit [...]
+ "content": "Commit Message 须知\n一个好的 commit message
应当一眼说清改了什么、为什么改。完整的来龙去脉留给关联的 Issue / Pull Request —— commit message
本身保持精炼。\n格式\n[Type-ISSUE_ID][Scope] Subject\n\n(可选 body —— 用要点列出主要改动)\n\n(可选
footer —— BREAKING CHANGE / Closes #xxx)\n\nHeader 必填，body 和 footer 可选。Subject
建议控制在 72 字符内，避免在 GitHub 上被截断。\nType（必填）\n\n\n\nType\n使用场景\n是否必须带 Issue
ID\n\n\n\n\nFeature\n用户可见的新功能\n是\n\n\nImprovement\n已有功能的增强（重构、性能、体验优化）\n是\n\n\nFix\nBug
修复\n是\n\n\nDoc\n仅文档变动\n是\n\n\nDSIP\n实现某个 DSIP 提案的变更\n是 [...]
"version": "dev",
"link": "/contribute/join/commit-message",
"title": "Commit Message 须知",
diff --git a/pages/doc/en-us/dev/contribute/join/commit-message.json
b/pages/doc/en-us/dev/contribute/join/commit-message.json
index 76a64e2d03..d2c4cf89f9 100644
--- a/pages/doc/en-us/dev/contribute/join/commit-message.json
+++ b/pages/doc/en-us/dev/contribute/join/commit-message.json
@@ -1,5 +1,5 @@
{
- "__html": "<h1 id=\"commit-message-notice\">Commit Message Notice</h1>\n<h3
id=\"preface\">Preface</h3>\n<p>A good commit message can help other developers
(or future developers) quickly understand the context of related changes, and
can also help project managers determine whether the commit is suitable for
inclusion in the release. But when we checked the commit logs of many open
source projects, we found an interesting problem. Some developers have very
good code quality, but the co [...]
+ "__html": "<h1 id=\"commit-message-notice\">Commit Message Notice</h1>\n<p>A
good commit message states <strong>what changed and why</strong> at a glance.
The full story belongs in the linked Issue / Pull Request — keep the commit
message itself concise.</p>\n<h2
id=\"format\">Format</h2>\n<pre><code>[Type-ISSUE_ID][Scope]
Subject\n\n(optional body — bullet list of the main changes)\n\n(optional
footer — BREAKING CHANGE / Closes #xxx)\n</code></pre>\n<p>Header is required;
body and foo [...]
"location": [
"Contribution",
"Join",
@@ -7,256 +7,97 @@
],
"structure": [
{
- "title": "Preface",
+ "title": "Format",
"children": [
{
- "title": "1：Clearly modify the content",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "1：clearly-modify-the-content"
+ "title": "Type (required)",
+ "children": [],
+ "anchor": "type-(required)"
},
{
- "title": "2：Associate the corresponding Pull Request or Issue",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "2：associate-the-corresponding-pull-request-or-issue"
+ "title": "Scope (optional)",
+ "children": [],
+ "anchor": "scope-(optional)"
},
{
- "title": "3：Unified format",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "3：unified-format"
+ "title": "Subject (required)",
+ "children": [],
+ "anchor": "subject-(required)"
+ },
+ {
+ "title": "Body (optional, recommended for non-trivial changes)",
+ "children": [],
+ "anchor": "body-(optional,-recommended-for-non-trivial-changes)"
+ },
+ {
+ "title": "Footer (optional)",
+ "children": [],
+ "anchor": "footer-(optional)"
}
],
- "anchor": "preface"
+ "anchor": "format"
},
{
- "title": "Commit Message RIP",
+ "title": "Examples",
"children": [
{
- "title": "1：Clearly modify the content",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "1：clearly-modify-the-content"
+ "title": "Type (required)",
+ "children": [],
+ "anchor": "type-(required)"
+ },
+ {
+ "title": "Scope (optional)",
+ "children": [],
+ "anchor": "scope-(optional)"
},
{
- "title": "2：Associate the corresponding Pull Request or Issue",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "2：associate-the-corresponding-pull-request-or-issue"
+ "title": "Subject (required)",
+ "children": [],
+ "anchor": "subject-(required)"
},
{
- "title": "3：Unified format",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "3：unified-format"
+ "title": "Body (optional, recommended for non-trivial changes)",
+ "children": [],
+ "anchor": "body-(optional,-recommended-for-non-trivial-changes)"
+ },
+ {
+ "title": "Footer (optional)",
+ "children": [],
+ "anchor": "footer-(optional)"
}
],
- "anchor": "commit-message-rip"
+ "anchor": "examples"
},
{
- "title": "Reference documents",
+ "title": "References",
"children": [
{
- "title": "1：Clearly modify the content",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "1：clearly-modify-the-content"
+ "title": "Type (required)",
+ "children": [],
+ "anchor": "type-(required)"
+ },
+ {
+ "title": "Scope (optional)",
+ "children": [],
+ "anchor": "scope-(optional)"
+ },
+ {
+ "title": "Subject (required)",
+ "children": [],
+ "anchor": "subject-(required)"
},
{
- "title": "2：Associate the corresponding Pull Request or Issue",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "2：associate-the-corresponding-pull-request-or-issue"
+ "title": "Body (optional, recommended for non-trivial changes)",
+ "children": [],
+ "anchor": "body-(optional,-recommended-for-non-trivial-changes)"
},
{
- "title": "3：Unified format",
- "children": [
- {
- "title": "Header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "For Example",
- "children": [],
- "anchor": "for-example"
- }
- ],
- "anchor": "3：unified-format"
+ "title": "Footer (optional)",
+ "children": [],
+ "anchor": "footer-(optional)"
}
],
- "anchor": "reference-documents"
+ "anchor": "references"
}
],
"title": "Commit Message Notice",
diff --git a/pages/doc/en-us/dev/contribute/join/pull-request.json
b/pages/doc/en-us/dev/contribute/join/pull-request.json
index 707c3cf95d..53549985b0 100644
--- a/pages/doc/en-us/dev/contribute/join/pull-request.json
+++ b/pages/doc/en-us/dev/contribute/join/pull-request.json
@@ -1,5 +1,5 @@
{
- "__html": "<h1 id=\"pull-request-notice\">Pull Request Notice</h1>\n<h2
id=\"preface\">Preface</h2>\n<p>Pull Request is a way of software cooperation,
which is a process of bringing code involving different functions into the
trunk. During this process, the code can be discussed, reviewed, and
modified.</p>\n<p>In Pull Request, we try not to discuss the implementation of
the code. The general implementation of the code and its logic should be
determined in Issue. In the Pull Request, w [...]
+ "__html": "<h1 id=\"pull-request-notice\">Pull Request Notice</h1>\n<h2
id=\"preface\">Preface</h2>\n<p>Pull Request is a way of software cooperation,
which is a process of bringing code involving different functions into the
trunk. During this process, the code can be discussed, reviewed, and
modified.</p>\n<p>In Pull Request, we try not to discuss the implementation of
the code. The general implementation of the code and its logic should be
determined in Issue. In the Pull Request, w [...]
"location": [
"Contribution",
"Join",
diff --git a/pages/doc/en-us/dev/contribute/join/submit-code.json
b/pages/doc/en-us/dev/contribute/join/submit-code.json
index c74a6316cf..7eb60db026 100644
--- a/pages/doc/en-us/dev/contribute/join/submit-code.json
+++ b/pages/doc/en-us/dev/contribute/join/submit-code.json
@@ -1,5 +1,5 @@
{
- "__html": "<h1 id=\"submit-code\">Submit Code</h1>\n<ul>\n<li>\n<p>First
from the remote repository
<em>https://github.com/apache/dolphinscheduler.git</em> fork a copy of the code
into your own repository</p>\n</li>\n<li>\n<p>There are currently three
branches in the remote repository:</p>\n<ul>\n<li>master normal
delivery branch\nAfter the stable release, merge the code from the stable
branch into the master.</li>\n<li>dev daily development
branch\nEvery day dev [...]
+ "__html": "<h1 id=\"submit-code\">Submit Code</h1>\n<ul>\n<li>\n<p>First
from the remote repository
<em>https://github.com/apache/dolphinscheduler.git</em> fork a copy of the code
into your own repository</p>\n</li>\n<li>\n<p>There are currently three
branches in the remote repository:</p>\n<ul>\n<li>master normal
delivery branch\nAfter the stable release, merge the code from the stable
branch into the master.</li>\n<li>dev daily development
branch\nEvery day dev [...]
"location": [
"Contribution",
"Join",
diff --git a/pages/doc/zh-cn/dev/contribute/join/commit-message.json
b/pages/doc/zh-cn/dev/contribute/join/commit-message.json
index de70fb16c2..e6559e952a 100644
--- a/pages/doc/zh-cn/dev/contribute/join/commit-message.json
+++ b/pages/doc/zh-cn/dev/contribute/join/commit-message.json
@@ -1,5 +1,5 @@
{
- "__html": "<h1 id=\"commit-message-须知\">Commit Message 须知</h1>\n<h3
id=\"前言\">前言</h3>\n<p>一个好的 commit message
是能够帮助其他的开发者（或者未来的开发者）快速理解相关变更的上下文，同时也可以帮助项目管理人员确定该提交是否适合包含在发行版中。但当我们在查看了很多开源项目的
commit log 后，发现一个有趣的问题，一部分开发者，代码质量很不错，但是 commit message
记录却比较混乱，当其他贡献者或者学习者在查看代码的时候，并不能通过 commit log 很直观的了解\n该提交前后变更的目的，正如 Peter
Hutterer 所言：Re-establishing the context of a piece of code is wasteful. We
can’t avoid it completely, so our efforts should go to reducing it as much as
possible. Commit m [...]
+ "__html": "<h1 id=\"commit-message-须知\">Commit Message 须知</h1>\n<p>一个好的
commit message 应当一眼说清<strong>改了什么、为什么改</strong>。完整的来龙去脉留给关联的 Issue / Pull
Request —— commit message 本身保持精炼。</p>\n<h2
id=\"格式\">格式</h2>\n<pre><code>[Type-ISSUE_ID][Scope] Subject\n\n(可选 body ——
用要点列出主要改动)\n\n(可选 footer —— BREAKING CHANGE / Closes
#xxx)\n</code></pre>\n<p>Header 必填，body 和 footer 可选。Subject 建议控制在 72 字符内，避免在
GitHub 上被截断。</p>\n<h3
id=\"type（必填）\">Type（必填）</h3>\n<table>\n<thead>\n<tr>\n<th>Type</th>\n<th [...]
"location": [
"贡献指南",
"如何参与",
@@ -7,256 +7,97 @@
],
"structure": [
{
- "title": "前言",
+ "title": "格式",
"children": [
{
- "title": "1：明确修改内容",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "1：明确修改内容"
+ "title": "Type（必填）",
+ "children": [],
+ "anchor": "type（必填）"
},
{
- "title": "2：关联相应的Pull Request 或者Issue",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "2：关联相应的pull-request-或者issue"
+ "title": "Scope（可选）",
+ "children": [],
+ "anchor": "scope（可选）"
},
{
- "title": "3：统一的格式",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "3：统一的格式"
+ "title": "Subject（必填）",
+ "children": [],
+ "anchor": "subject（必填）"
+ },
+ {
+ "title": "Body（可选，非平凡改动建议写）",
+ "children": [],
+ "anchor": "body（可选，非平凡改动建议写）"
+ },
+ {
+ "title": "Footer（可选）",
+ "children": [],
+ "anchor": "footer（可选）"
}
],
- "anchor": "前言"
+ "anchor": "格式"
},
{
- "title": "Commit Message RIP",
+ "title": "示例",
"children": [
{
- "title": "1：明确修改内容",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "1：明确修改内容"
+ "title": "Type（必填）",
+ "children": [],
+ "anchor": "type（必填）"
+ },
+ {
+ "title": "Scope（可选）",
+ "children": [],
+ "anchor": "scope（可选）"
},
{
- "title": "2：关联相应的Pull Request 或者Issue",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "2：关联相应的pull-request-或者issue"
+ "title": "Subject（必填）",
+ "children": [],
+ "anchor": "subject（必填）"
},
{
- "title": "3：统一的格式",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "3：统一的格式"
+ "title": "Body（可选，非平凡改动建议写）",
+ "children": [],
+ "anchor": "body（可选，非平凡改动建议写）"
+ },
+ {
+ "title": "Footer（可选）",
+ "children": [],
+ "anchor": "footer（可选）"
}
],
- "anchor": "commit-message-rip"
+ "anchor": "示例"
},
{
- "title": "参考文档",
+ "title": "参考资料",
"children": [
{
- "title": "1：明确修改内容",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "1：明确修改内容"
+ "title": "Type（必填）",
+ "children": [],
+ "anchor": "type（必填）"
+ },
+ {
+ "title": "Scope（可选）",
+ "children": [],
+ "anchor": "scope（可选）"
+ },
+ {
+ "title": "Subject（必填）",
+ "children": [],
+ "anchor": "subject（必填）"
},
{
- "title": "2：关联相应的Pull Request 或者Issue",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "2：关联相应的pull-request-或者issue"
+ "title": "Body（可选，非平凡改动建议写）",
+ "children": [],
+ "anchor": "body（可选，非平凡改动建议写）"
},
{
- "title": "3：统一的格式",
- "children": [
- {
- "title": "header",
- "children": [],
- "anchor": "header"
- },
- {
- "title": "Body",
- "children": [],
- "anchor": "body"
- },
- {
- "title": "Footer",
- "children": [],
- "anchor": "footer"
- },
- {
- "title": "举个例子",
- "children": [],
- "anchor": "举个例子"
- }
- ],
- "anchor": "3：统一的格式"
+ "title": "Footer（可选）",
+ "children": [],
+ "anchor": "footer（可选）"
}
],
- "anchor": "参考文档"
+ "anchor": "参考资料"
}
],
"title": "Commit Message 须知",
diff --git a/pages/doc/zh-cn/dev/contribute/join/pull-request.json
b/pages/doc/zh-cn/dev/contribute/join/pull-request.json
index 7e6689f3fe..c64b51a44a 100644
--- a/pages/doc/zh-cn/dev/contribute/join/pull-request.json
+++ b/pages/doc/zh-cn/dev/contribute/join/pull-request.json
@@ -1,5 +1,5 @@
{
- "__html": "<h1 id=\"pull-request-须知\">Pull Request 须知</h1>\n<h2
id=\"前言\">前言</h2>\n<p>Pull Request
本质上是一种软件的合作方式，是将涉及不同功能的代码，纳入主干的一种流程。这个过程中，可以进行讨论、审核和修改代码。</p>\n<p>在 Pull
Request 中尽量不讨论代码的实现方案，代码及其逻辑的大体实现方案应该尽量在\nIssue 或者邮件列表中被讨论确定，在 Pull Request
中我们尽量只关注代码的格式以及代码规范等信息，从而避免实现方式的意见不同而导致\nwaste time。</p>\n<h2
id=\"规范\">规范</h2>\n<h3 id=\"pull-request-标题\">Pull Request
标题</h3>\n<p>标题格式：[<code>Pull Request 类型</code>-<code>Issue
号</code>][<code>模块名</code>] <code>Pull Request 描述</code></p>\n [...]
+ "__html": "<h1 id=\"pull-request-须知\">Pull Request 须知</h1>\n<h2
id=\"前言\">前言</h2>\n<p>Pull Request
本质上是一种软件的合作方式，是将涉及不同功能的代码，纳入主干的一种流程。这个过程中，可以进行讨论、审核和修改代码。</p>\n<p>在 Pull
Request 中尽量不讨论代码的实现方案，代码及其逻辑的大体实现方案应该尽量在\nIssue 或者邮件列表中被讨论确定，在 Pull Request
中我们尽量只关注代码的格式以及代码规范等信息，从而避免实现方式的意见不同而导致\nwaste time。</p>\n<h2
id=\"规范\">规范</h2>\n<h3 id=\"pull-request-标题\">Pull Request
标题</h3>\n<p>标题格式：[<code>Pull Request 类型</code>-<code>Issue
号</code>][<code>模块名</code>] <code>Pull Request 描述</code></p>\n [...]
"location": [
"贡献指南",
"如何参与",
diff --git a/pages/doc/zh-cn/dev/contribute/join/submit-code.json
b/pages/doc/zh-cn/dev/contribute/join/submit-code.json
index 315babd294..986db8c92b 100644
--- a/pages/doc/zh-cn/dev/contribute/join/submit-code.json
+++ b/pages/doc/zh-cn/dev/contribute/join/submit-code.json
@@ -1,5 +1,5 @@
{
- "__html": "<h1
id=\"提交代码\">提交代码</h1>\n<ul>\n<li>\n<p>首先从远端仓库<em>https://github.com/apache/dolphinscheduler.git</em>
fork一份代码到自己的仓库中</p>\n</li>\n<li>\n<p>远端仓库中目前有三个分支：</p>\n<ul>\n<li>\n<p>master
正常交付分支\n发布稳定版本以后，将稳定版本分支的代码合并到master上。</p>\n</li>\n<li>\n<p>dev
日常开发分支\n日常dev开发分支，新提交的代码都可以pull
request到这个分支上。</p>\n</li>\n<li>\n<p>branch-1.0.0
发布版本分支\n发布版本分支，后续会有2.0...等版本分支。</p>\n</li>\n</ul>\n</li>\n<li>\n<p>把自己仓库clone到本地</p>\n<p><code>
git clone https://github.com/apache/dolphinscheduler [...]
+ "__html": "<h1
id=\"提交代码\">提交代码</h1>\n<ul>\n<li>\n<p>首先从远端仓库<em>https://github.com/apache/dolphinscheduler.git</em>
fork一份代码到自己的仓库中</p>\n</li>\n<li>\n<p>远端仓库中目前有三个分支：</p>\n<ul>\n<li>\n<p>master
正常交付分支\n发布稳定版本以后，将稳定版本分支的代码合并到master上。</p>\n</li>\n<li>\n<p>dev
日常开发分支\n日常dev开发分支，新提交的代码都可以pull
request到这个分支上。</p>\n</li>\n<li>\n<p>branch-1.0.0
发布版本分支\n发布版本分支，后续会有2.0...等版本分支。</p>\n</li>\n</ul>\n</li>\n<li>\n<p>把自己仓库clone到本地</p>\n<p><code>
git clone https://github.com/apache/dolphinscheduler [...]
"location": [
"贡献指南",
"如何参与",
