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
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
a1cc0c6f
Commit
a1cc0c6f
authored
Jun 14, 2018
by
Marcel Amirault
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update CONTRIBUTING.md to fix links
parent
b4f29f58
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
CONTRIBUTING.md
CONTRIBUTING.md
+2
-2
No files found.
CONTRIBUTING.md
View file @
a1cc0c6f
...
...
@@ -627,7 +627,7 @@ the feature you contribute through all of these steps.
1.
Working and clean code that is commented where needed
1.
[
Unit, integration, and system tests
][
testing
]
that pass on the CI server
1.
Performance/scalability implications have been considered, addressed, and tested
1.
[
Documented
][
doc-
styleguide
]
in the
`/doc`
directory
1.
[
Documented
][
doc-
guidelines
]
in the
`/doc`
directory
1.
[
Changelog entry added
][
changelog
]
, if necessary
1.
Reviewed and any concerns are addressed
1.
Merged by a project maintainer
...
...
@@ -664,7 +664,7 @@ merge request:
contributors to enhance security
1.
[
Database Migrations
](
doc/development/migration_style_guide.md
)
1.
[
Markdown
](
http://www.cirosantilli.com/markdown-styleguide
)
1.
[
Documentation styleguide
]
[
doc-styleguide
]
1.
[
Documentation styleguide
]
(
https://docs.gitlab.com/ee/development/documentation/styleguide.html
)
1.
Interface text should be written subjectively instead of objectively. It
should be the GitLab core team addressing a person. It should be written in
present time and never use past tense (has been/was). For example instead
...
...
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