Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
a1db103a
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
提交
a1db103a
编写于
2月 14, 2016
作者:
N
nozo
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
fix some links
上级
dc3ea7eb
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
13 addition
and
13 deletion
+13
-13
CONTRIBUTING.md
CONTRIBUTING.md
+13
-13
未找到文件。
CONTRIBUTING.md
浏览文件 @
a1db103a
...
@@ -34,7 +34,7 @@ source edition, and GitLab Enterprise Edition (EE) which is our commercial
...
@@ -34,7 +34,7 @@ source edition, and GitLab Enterprise Edition (EE) which is our commercial
edition. Throughout this guide you will see references to CE and EE for
edition. Throughout this guide you will see references to CE and EE for
abbreviation.
abbreviation.
If you have read this guide and want to know how the GitLab
[
core
-team
][
]
If you have read this guide and want to know how the GitLab
[
core
team
][
core-team
]
operates please see
[
the GitLab contributing process
](
PROCESS.md
)
.
operates please see
[
the GitLab contributing process
](
PROCESS.md
)
.
## Contributor license agreement
## Contributor license agreement
...
@@ -68,10 +68,10 @@ for audiences of all ages.
...
@@ -68,10 +68,10 @@ for audiences of all ages.
## Helping others
## Helping others
Please help other GitLab users when you can. The channels people will reach out
Please help other GitLab users when you can. The channels people will reach out
on can be found on the
[
getting help page
][]
.
on can be found on the
[
getting help page
][
getting-help
]
.
Sign up for the mailing list, answer GitLab questions on StackOverflow or
Sign up for the mailing list, answer GitLab questions on StackOverflow or
respond in the IRC channel. You can also sign up on
[
CodeTriage
][]
to help with
respond in the IRC channel. You can also sign up on
[
CodeTriage
][
codetriage
]
to help with
the remaining issues on the GitHub issue tracker.
the remaining issues on the GitHub issue tracker.
## I want to contribute!
## I want to contribute!
...
@@ -115,7 +115,7 @@ For feature proposals for EE, open an issue on the
...
@@ -115,7 +115,7 @@ For feature proposals for EE, open an issue on the
In order to help track the feature proposals, we have created a
In order to help track the feature proposals, we have created a
[
`feature proposal`
][
fpl
]
label. For the time being, users that are not members
[
`feature proposal`
][
fpl
]
label. For the time being, users that are not members
of the project cannot add labels. You can instead ask one of the
[
core team
][]
of the project cannot add labels. You can instead ask one of the
[
core team
][
core-team
]
members to add the label
`feature proposal`
to the issue.
members to add the label
`feature proposal`
to the issue.
Please keep feature proposals as small and simple as possible, complex ones
Please keep feature proposals as small and simple as possible, complex ones
...
@@ -299,8 +299,8 @@ to us than having a minimal commit log. The smaller an MR is the more likely it
...
@@ -299,8 +299,8 @@ to us than having a minimal commit log. The smaller an MR is the more likely it
is it will be merged (quickly). After that you can send more MRs to enhance it.
is it will be merged (quickly). After that you can send more MRs to enhance it.
For examples of feedback on merge requests please look at already
For examples of feedback on merge requests please look at already
[
closed merge requests
][]
. If you would like quick feedback on your merge
[
closed merge requests
][
closed-merge-requests
]
. If you would like quick feedback on your merge
request feel free to mention one of the Merge Marshalls of the
[
core team
][]
.
request feel free to mention one of the Merge Marshalls of the
[
core team
][
core-team
]
.
Please ensure that your merge request meets the contribution acceptance criteria.
Please ensure that your merge request meets the contribution acceptance criteria.
When having your code reviewed and when reviewing merge requests please take the
When having your code reviewed and when reviewing merge requests please take the
...
@@ -369,7 +369,7 @@ Like all merge requests the target should be master so all bugfixes are in maste
...
@@ -369,7 +369,7 @@ Like all merge requests the target should be master so all bugfixes are in maste
## Definition of done
## Definition of done
If you contribute to GitLab please know that changes involve more than just
If you contribute to GitLab please know that changes involve more than just
code. We have the following
[
definition of done
][]
. Please ensure you support
code. We have the following
[
definition of done
][
definition-of-done
]
. Please ensure you support
the feature you contribute through all of these steps.
the feature you contribute through all of these steps.
1.
Description explaining the relevancy (see following item)
1.
Description explaining the relevancy (see following item)
...
@@ -448,12 +448,12 @@ when an individual is representing the project or its community.
...
@@ -448,12 +448,12 @@ when an individual is representing the project or its community.
Instances of abusive, harassing, or otherwise unacceptable behavior can be
Instances of abusive, harassing, or otherwise unacceptable behavior can be
reported by emailing
`contact@gitlab.com`
.
reported by emailing
`contact@gitlab.com`
.
This Code of Conduct is adapted from the
[
Contributor Covenant
][]
, version 1.1.0,
This Code of Conduct is adapted from the
[
Contributor Covenant
][
contributor-covenant
]
, version 1.1.0,
available at
[
http://contributor-covenant.org/version/1/1/0/
](
http://contributor-covenant.org/version/1/1/0/
)
.
available at
[
http://contributor-covenant.org/version/1/1/0/
](
http://contributor-covenant.org/version/1/1/0/
)
.
[
core-team
]:
https://about.gitlab.com/core-team/
[
core-team
]:
https://about.gitlab.com/core-team/
[
getting
help page
]:
https://about.gitlab.com/getting-help/
[
getting
-help
]:
https://about.gitlab.com/getting-help/
[
C
odetriage
]:
http://www.codetriage.com/gitlabhq/gitlabhq
[
c
odetriage
]:
http://www.codetriage.com/gitlabhq/gitlabhq
[
up-for-grabs
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=up-for-grabs
[
up-for-grabs
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=up-for-grabs
[
medium-up-for-grabs
]:
https://medium.com/@kentcdodds/first-timers-only-78281ea47455
[
medium-up-for-grabs
]:
https://medium.com/@kentcdodds/first-timers-only-78281ea47455
[
ce-tracker
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues
[
ce-tracker
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues
...
@@ -467,9 +467,9 @@ available at [http://contributor-covenant.org/version/1/1/0/](http://contributor
...
@@ -467,9 +467,9 @@ available at [http://contributor-covenant.org/version/1/1/0/](http://contributor
[
github-mr-tracker
]:
https://github.com/gitlabhq/gitlabhq/pulls
[
github-mr-tracker
]:
https://github.com/gitlabhq/gitlabhq/pulls
[
gdk
]:
https://gitlab.com/gitlab-org/gitlab-development-kit
[
gdk
]:
https://gitlab.com/gitlab-org/gitlab-development-kit
[
git-squash
]:
https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits
[
git-squash
]:
https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits
[
closed
merge
requests
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?assignee_id=&label_name=&milestone_id=&scope=&sort=&state=closed
[
closed
-merge-
requests
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?assignee_id=&label_name=&milestone_id=&scope=&sort=&state=closed
[
definition
of
done
]:
http://guide.agilealliance.org/guide/definition-of-done.html
[
definition
-of-
done
]:
http://guide.agilealliance.org/guide/definition-of-done.html
[
Contributor C
ovenant
]:
http://contributor-covenant.org
[
contributor-c
ovenant
]:
http://contributor-covenant.org
[
rss-source
]:
https://github.com/bbatsov/ruby-style-guide/blob/master/README.md#source-code-layout
[
rss-source
]:
https://github.com/bbatsov/ruby-style-guide/blob/master/README.md#source-code-layout
[
rss-naming
]:
https://github.com/bbatsov/ruby-style-guide/blob/master/README.md#naming
[
rss-naming
]:
https://github.com/bbatsov/ruby-style-guide/blob/master/README.md#naming
[
doc-styleguide
]:
doc/development/doc_styleguide.md
"Documentation styleguide"
[
doc-styleguide
]:
doc/development/doc_styleguide.md
"Documentation styleguide"
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录