This is an automated email from the ASF dual-hosted git repository.
lidongdai pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/incubator-dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new 9f274f0 fix error, commit_message -> commit-message
new 326acaa Merge pull request #205 from dailidong/master
9f274f0 is described below
commit 9f274f07aeac3a6984f9dcf2f85864a6a66b00da
Author: dailidong <[email protected]>
AuthorDate: Sun Nov 1 16:50:53 2020 +0800
fix error, commit_message -> commit-message
---
docs/en-us/development/contribute.md | 78 ++++++++++++++++++------------------
docs/zh-cn/development/contribute.md | 2 +-
md_json/docs.json | 4 +-
site_config/development.js | 2 +-
4 files changed, 43 insertions(+), 43 deletions(-)
diff --git a/docs/en-us/development/contribute.md
b/docs/en-us/development/contribute.md
index 1d2f88b..f8e1402 100644
--- a/docs/en-us/development/contribute.md
+++ b/docs/en-us/development/contribute.md
@@ -1,40 +1,40 @@
-## Contribute
-
-First of all, thank you very much for choosing and using DolphinScheduler, and
welcome to join the DolphinScheduler family!
-
-We encourage any form of participation in the community that will eventually
become Committer or PPMC Such as:
-* Problems will be encountered via github on the
[issue](https://github.com/apache/incubator-dolphinscheduler/issues) form
feedback out.
-* Answer the issue questions that others are asking.
-* Help improve the documentation.
-* Help your project add test cases.
-* Add comments to the code.
-* Submit a PR that fixes the bug or Feature.
-* Publish application case practice, scheduling process analysis, or technical
articles related to scheduling.
-* Help promote DolphinScheduler, participate in technical conferences or
meetup, sharing and more.
-
-Welcome to the contributing team and join open source starting with submitting
your first PR.
- - For example, add code comments or find "easy to fix" tags or some very
simple issue (misspellings, etc.) and so on, first familiarize yourself with
the submission process through the first simple PR.
-
-Note: Contributions are not limited to PR Only, but contribute to the
development of the project.
-
-I'm sure you'll benefit from open source by participating in DolphinScheduler!
-
-### 1. Participate in documentation contributions.
-
-Refer to the [Submit Guide-Document Notice](document.md)
-
-### 2. Participate in code contributions.
-
-Refer to the [Submit Guide-Issue Notice](issue.md), [Submit Guide-Pull Request
Notice](pull-request.md), [Submit Guide-Commit Message
Notice](commit_message.md)
-
-### 3. How to pick up an Issue and submit a Pull Request.
-
-If you want to implement a Feature or fix a Bug. Please refer to the following:
-
-* All Bugs and the new Features are recommended and managed using the Issues
Page.
-* If you want to develop a Feature, first reply to the Issue associated with
that feature, indicating that you are currently working on it. And set yourself
a "deadline" when to Submit the Feature, and add it in the reply comment.
-* It's a good idea to find a mentor (or an instructor) in the core
contributors who gives immediate feedback on design and functional
implementation.
-* You should create a new branch to start your work, to get the name of the
branch refer to the [Submit Guide-Pull Request Notice](pull-request.md). For
example, if you want to complete the feature and submit Issue 111, your branch
name should be feature-111. The feature name can be determined after discussion
with the instructor.
-* When you're done, send a Pull Request to incubator-dolphinscheduler, please
refer to the《[Submit Guide-Submit Pull Request Process](submit-code.md)》
-
+## Contribute
+
+First of all, thank you very much for choosing and using DolphinScheduler, and
welcome to join the DolphinScheduler family!
+
+We encourage any form of participation in the community that will eventually
become Committer or PPMC Such as:
+* Problems will be encountered via github on the
[issue](https://github.com/apache/incubator-dolphinscheduler/issues) form
feedback out.
+* Answer the issue questions that others are asking.
+* Help improve the documentation.
+* Help your project add test cases.
+* Add comments to the code.
+* Submit a PR that fixes the bug or Feature.
+* Publish application case practice, scheduling process analysis, or technical
articles related to scheduling.
+* Help promote DolphinScheduler, participate in technical conferences or
meetup, sharing and more.
+
+Welcome to the contributing team and join open source starting with submitting
your first PR.
+ - For example, add code comments or find "easy to fix" tags or some very
simple issue (misspellings, etc.) and so on, first familiarize yourself with
the submission process through the first simple PR.
+
+Note: Contributions are not limited to PR Only, but contribute to the
development of the project.
+
+I'm sure you'll benefit from open source by participating in DolphinScheduler!
+
+### 1. Participate in documentation contributions.
+
+Refer to the [Submit Guide-Document Notice](document.md)
+
+### 2. Participate in code contributions.
+
+Refer to the [Submit Guide-Issue Notice](issue.md), [Submit Guide-Pull Request
Notice](pull-request.md), [Submit Guide-Commit Message
Notice](commit-message.md)
+
+### 3. How to pick up an Issue and submit a Pull Request.
+
+If you want to implement a Feature or fix a Bug. Please refer to the following:
+
+* All Bugs and the new Features are recommended and managed using the Issues
Page.
+* If you want to develop a Feature, first reply to the Issue associated with
that feature, indicating that you are currently working on it. And set yourself
a "deadline" when to Submit the Feature, and add it in the reply comment.
+* It's a good idea to find a mentor (or an instructor) in the core
contributors who gives immediate feedback on design and functional
implementation.
+* You should create a new branch to start your work, to get the name of the
branch refer to the [Submit Guide-Pull Request Notice](pull-request.md). For
example, if you want to complete the feature and submit Issue 111, your branch
name should be feature-111. The feature name can be determined after discussion
with the instructor.
+* When you're done, send a Pull Request to incubator-dolphinscheduler, please
refer to the《[Submit Guide-Submit Pull Request Process](submit-code.md)》
+
If you want to submit a Pull Request to complete a Feature or fix a Bug, it is
recommended that you start with the `good first issue`, `easy-to-fix` issues,
complete a small function to submit, do not change too many files at a time,
changing too many files will also put a lot of pressure on Reviewers, it is
recommended to submit them through multiple Pull Requests, not all at once.
\ No newline at end of file
diff --git a/docs/zh-cn/development/contribute.md
b/docs/zh-cn/development/contribute.md
index ea47f5a..18fc5f8 100644
--- a/docs/zh-cn/development/contribute.md
+++ b/docs/zh-cn/development/contribute.md
@@ -25,7 +25,7 @@
### 2. 参与代码贡献
-参考[参与贡献 Issue 需知](issue.md)，[参与贡献 Pull Request 需知](pull-request.md)，[参与贡献
CommitMessage 需知](commit_message.md)
+参考[参与贡献 Issue 需知](issue.md)，[参与贡献 Pull Request 需知](pull-request.md)，[参与贡献
CommitMessage 需知](commit-message.md)
### 3. 如何领取 Issue，提交 Pull Request
diff --git a/md_json/docs.json b/md_json/docs.json
index 9df69c9..7d93170 100755
--- a/md_json/docs.json
+++ b/md_json/docs.json
@@ -103,8 +103,8 @@
"meta": {}
},
{
- "filename": "commit_message.md",
- "link": "/zh-cn/docs/development/commit_message.html",
+ "filename": "commit-message.md",
+ "link": "/zh-cn/docs/development/commit-message.html",
"meta": {}
},
{
diff --git a/site_config/development.js b/site_config/development.js
index 76d7f33..b60c42f 100755
--- a/site_config/development.js
+++ b/site_config/development.js
@@ -144,7 +144,7 @@ export default {
},
{
title: '参与贡献-CommitMessage需知',
- link: '/zh-cn/docs/development/commit_message.html',
+ link: '/zh-cn/docs/development/commit-message.html',
},
{
title: '参与贡献-微基准测试',
