Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gitlab-ce
Commits
da4aaaac
Commit
da4aaaac
authored
Apr 28, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix links to core team page
[ci skip]
parent
8b817f59
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
5 deletions
+4
-5
CONTRIBUTING.md
CONTRIBUTING.md
+4
-5
No files found.
CONTRIBUTING.md
View file @
da4aaaac
...
...
@@ -38,7 +38,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
abbreviation.
If you have read this guide and want to know how the GitLab
[
core team
]
[
core-team
]
If you have read this guide and want to know how the GitLab [core team]
operates please see
[
the GitLab contributing process
](
PROCESS.md
)
.
## Contributor license agreement
...
...
@@ -135,7 +135,7 @@ For feature proposals for EE, open an issue on the
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
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]
members to add the label
`feature proposal`
to the issue or add the following
code snippet right after your description in a new line:
`~"feature proposal"`
.
...
...
@@ -345,8 +345,7 @@ 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
[
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 in the
[
core team
][
core-team
]
or one of the
[
Merge request coaches
](
https://about.gitlab.com/team/
)
.
[
core team] or one of the [Merge request coaches
](
https://about.gitlab.com/team/
)
.
Please ensure that your merge request meets the contribution acceptance criteria.
When having your code reviewed and when reviewing merge requests please take the
...
...
@@ -498,7 +497,7 @@ reported by emailing `contact@gitlab.com`.
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/
)
.
[
core
-
team
]:
https://about.gitlab.com/core-team/
[
core
team
]:
https://about.gitlab.com/core-team/
[
getting-help
]:
https://about.gitlab.com/getting-help/
[
codetriage
]:
http://www.codetriage.com/gitlabhq/gitlabhq
[
up-for-grabs
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=up-for-grabs
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment