This is an automated email from the ASF dual-hosted git repository.
github-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 e139e11 Automated deployment: 6b03f1fde2e14578f346228aee169ec2139f8a31
e139e11 is described below
commit e139e1123ab87e12b6002d436086f222a4a796a8
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Sun Dec 5 14:01:37 2021 +0000
Automated deployment: 6b03f1fde2e14578f346228aee169ec2139f8a31
---
en-us/community/development/pull-request.html | 6 ++++--
en-us/community/development/pull-request.json | 2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/en-us/community/development/pull-request.html
b/en-us/community/development/pull-request.html
index da1e43c..ea05c7f 100644
--- a/en-us/community/development/pull-request.html
+++ b/en-us/community/development/pull-request.html
@@ -15,7 +15,7 @@
<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>
<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, we only focus on the code format and code specification,
so as to avoid wasting time caused by different opinions on implementation.</p>
<h2>Specification</h2>
-<h3>Pull Request title</h3>
+<h3>Pull Request Title</h3>
<p>Title Format: [<code>Pull Request Type</code>-<code>Issue
No</code>][<code>Module Name</code>] <code>Pull Request Description</code></p>
<p>The corresponding relationship between <code>Pull Request Type</code> and
<code>Issue Type</code> is as follows:</p>
<table>
@@ -55,7 +55,9 @@
</tbody>
</table>
<p><code>Issue No</code> refers to the Issue number corresponding to the
current Pull Request to be resolved, <code>Module Name</code> is the same as
the <code>Module Name</code> of Issue.</p>
-<h3>Pull Request content</h3>
+<h3>Pull Request Branch</h3>
+<p>Branch name format: <code>Pull Request type</code>-<code>Issue
number</code>. e.g. Feature-3333</p>
+<h3>Pull Request Content</h3>
<p>Please refer to the commit message section.</p>
<h3>Pull Request Code Style</h3>
<p>Code style is the thing you have to consider when you submit pull request
for DolphinScheduler. We using <a
href="https://checkstyle.sourceforge.io";>Checkstyle</a>, a development tool to
help programmers write Java code that adheres to a coding standard, in CI to
keep DolphinScheduler codebase in the same style. Your pull request could not
be merged if your code style checker failed. You could format your code by
<em>Checkstyle</em> in your local environment before you submit your pul [...]
diff --git a/en-us/community/development/pull-request.json
b/en-us/community/development/pull-request.json
index 99b3b66..8bc58d4 100644
--- a/en-us/community/development/pull-request.json
+++ b/en-us/community/development/pull-request.json
@@ -1,6 +1,6 @@
{
"filename": "pull-request.md",
- "__html": "<h1>Pull Request Notice</h1>\n<h2>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, we only focus
on the code format and code s [...]
+ "__html": "<h1>Pull Request Notice</h1>\n<h2>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, we only focus
on the code format and code s [...]
"link": "/dist/en-us/community/development/pull-request.html",
"meta": {}
}
\ No newline at end of file
