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 af7c096 chore: fix case of GitHub (#301)
af7c096 is described below
commit af7c0969eff97ff0b9414fded84af312ef0f0e17
Author: John Bampton <[email protected]>
AuthorDate: Sun Feb 28 00:16:52 2021 +1000
chore: fix case of GitHub (#301)
---
community/en-us/development/commit-message.md | 2 +-
community/en-us/release.md | 2 +-
community/zh-cn/development/commit-message.md | 2 +-
community/zh-cn/release.md | 4 ++--
site_config/community.jsx | 4 ++--
site_config/home.jsx | 4 ++--
6 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/community/en-us/development/commit-message.md
b/community/en-us/development/commit-message.md
index 0c95173..26ac13a 100644
--- a/community/en-us/development/commit-message.md
+++ b/community/en-us/development/commit-message.md
@@ -19,7 +19,7 @@ A commit message should clearly state what issues (bug fixes,
function enhanceme
#### 2：Associate the corresponding Pull Request or Issue
-When our changes are large, the commit message should best be associated with
the relevant Issue or Pull Request on Github, so that our developers can
quickly understand the context of the code submission through the associated
information when reviewing the code. If the current commit is for an issue,
then the issue can be closed in the Footer section.
+When our changes are large, the commit message should best be associated with
the relevant Issue or Pull Request on GitHub, so that our developers can
quickly understand the context of the code submission through the associated
information when reviewing the code. If the current commit is for an issue,
then the issue can be closed in the Footer section.
#### 3：Unified format
diff --git a/community/en-us/release.md b/community/en-us/release.md
index 15d3c53..8f7c816 100644
--- a/community/en-us/release.md
+++ b/community/en-us/release.md
@@ -165,7 +165,7 @@ mvn release:prepare -Prelease -Darguments="-DskipTests"
-DautoVersionSubmodules=
It is basically the same as the previous rehearsal command, but deleting
-DdryRun=true parameter.
--DpushChanges=false：do not submit the edited version number and tag to Github
automatically.
+-DpushChanges=false：do not submit the edited version number and tag to GitHub
automatically.
After making sure there is no mistake in local files, submit them to GitHub.
diff --git a/community/zh-cn/development/commit-message.md
b/community/zh-cn/development/commit-message.md
index c086e32..9325960 100644
--- a/community/zh-cn/development/commit-message.md
+++ b/community/zh-cn/development/commit-message.md
@@ -12,7 +12,7 @@ commit message 应该明确说明该提交解决了哪些问题（bug 修复、
#### 2：关联相应的Pull Request 或者Issue
-当我们的改动较大的时候，commit message 最好能够关联 Github 上的相关 Issue 或者 Pull
Request，这样，我们的开发者在查阅代码的时候能够通过关联信息较为迅速的了解改代码提交的上下文情景，如果当前 commit 针对某个
issue，那么可以在 Footer 部分关闭这个 issue。
+当我们的改动较大的时候，commit message 最好能够关联 GitHub 上的相关 Issue 或者 Pull
Request，这样，我们的开发者在查阅代码的时候能够通过关联信息较为迅速的了解改代码提交的上下文情景，如果当前 commit 针对某个
issue，那么可以在 Footer 部分关闭这个 issue。
#### 3：统一的格式
diff --git a/community/zh-cn/release.md b/community/zh-cn/release.md
index 2588830..ca0687c 100644
--- a/community/zh-cn/release.md
+++ b/community/zh-cn/release.md
@@ -175,7 +175,7 @@ mvn release:prepare -Prelease -Darguments="-DskipTests"
-DautoVersionSubmodules=
和上一步演练的命令基本相同，去掉了-DdryRun=true参数。
--DpushChanges=false：不要将修改后的版本号和tag自动提交至Github。
+-DpushChanges=false：不要将修改后的版本号和tag自动提交至GitHub。
如果遇到以下错误，请配置git邮箱为自己的apache邮箱和apache账号名
```shell
[ERROR] *** Please tell me who you are.
@@ -318,7 +318,7 @@ gpg --verify
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinschedu
- 只存在文本文件，不存在二进制文件
- 所有文件的开头都有ASF许可证
- 能够正确编译，单元测试可以通过 (mvn install)
-- 版本内容与Github上tag的内容相符 (diff -r a verify_dir tag_dir)
+- 版本内容与GitHub上tag的内容相符 (diff -r a verify_dir tag_dir)
- 检查是否有多余文件或文件夹，例如空文件夹等
#### 检查二进制包的文件内容
diff --git a/site_config/community.jsx b/site_config/community.jsx
index fc48da0..725d73d 100644
--- a/site_config/community.jsx
+++ b/site_config/community.jsx
@@ -177,7 +177,7 @@ export default {
{
img: '/img/issue.png',
title: 'Issue',
- content: <span>Reporting issues via <a
href="https://github.com/apache/incubator-dolphinscheduler/issues";>Github
issues</a>.</span>,
+ content: <span>Reporting issues via <a
href="https://github.com/apache/incubator-dolphinscheduler/issues";>GitHub
issues</a>.</span>,
},
{
img: '/img/documents.png',
@@ -368,7 +368,7 @@ export default {
{
img: '/img/issue.png',
title: '报告缺陷',
- content: <span>通过<a
href="https://github.com/apache/incubator-dolphinscheduler/issues";> Github
issues </a>报告缺陷。</span>,
+ content: <span>通过<a
href="https://github.com/apache/incubator-dolphinscheduler/issues";> GitHub
issues </a>报告缺陷。</span>,
},
{
img: '/img/documents.png',
diff --git a/site_config/home.jsx b/site_config/home.jsx
index 96fd4c6..48574f7 100644
--- a/site_config/home.jsx
+++ b/site_config/home.jsx
@@ -12,7 +12,7 @@ export default {
type: 'primary',
},
{
- text: '查看Github',
+ text: '查看GitHub',
link: 'https://github.com/apache/incubator-dolphinscheduler',
type: 'normal',
},
@@ -65,7 +65,7 @@ export default {
type: 'primary',
},
{
- text: 'View on Github',
+ text: 'View on GitHub',
link: 'https://github.com/apache/incubator-dolphinscheduler',
type: 'normal',
},
