Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
GitLab
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Commits
Open sidebar
projects.thm.de
GitLab
Commits
43ecf68a
Commit
43ecf68a
authored
Apr 07, 2014
by
dosire
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Small edit.
parent
ac906b42
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
PROCESS.md
PROCESS.md
+1
-1
No files found.
PROCESS.md
View file @
43ecf68a
...
...
@@ -17,7 +17,7 @@ Below we describe the contributing process to GitLab for two reasons. So that co
-
Responds to merge requests the issue team mentions them in and monitors for new merge requests
-
Provides feedback to the merge request submitter to improve the merge request (style, tests, etc.)
-
Mark
s
merge requests 'ready-for-merge' when they meet the contribution guidelines
-
Mark merge requests 'ready-for-merge' when they meet the contribution guidelines
-
Mention developer(s) based on the
[
list of members and their specialities
](
https://www.gitlab.com/core-team/
)
-
Closes merge requests with no feedback from the reporter for two weeks
...
...
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