summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKamil Trzciński <ayufan@ayufan.eu>2015-07-21 08:45:07 +0000
committerKamil Trzciński <ayufan@ayufan.eu>2015-07-21 08:45:07 +0000
commit7728125c3e3474fef153c0037355c20ec72868b0 (patch)
treee8f7dd0fcd2870a284ba571240ba73e0a243ab19
parenta7de1f3dfb8e0fd4127d62a483acd6921c7bc221 (diff)
parente25e70f9e284b3399c108c3d86358b0f599d928e (diff)
downloadgitlab-ci-7728125c3e3474fef153c0037355c20ec72868b0.tar.gz
Merge branch 'contributing_spelling' into 'master'
fix small spelling issue in CONTRIBUTING.md Fix mispelling of 'submission' in contributing doc. See merge request !201
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fb22c47..a89c593 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -32,7 +32,7 @@ If you can, please submit a merge request with the fix or improvements including
1. The MR description should give a motive for your change and the method you used to achieve it
1. If the MR changes the UI it should include before and after screenshots
1. Link relevant [issues](https://gitlab.com/gitlab-org/gitlab-ci/issues) and/or [feedback items](http://feedback.gitlab.com/) from the merge request description and leave a comment on them with a link back to the MR
-1. Be prepared to answer questions and incorporate feedback even if requests for this arrive weeks or months after your MR submittion
+1. Be prepared to answer questions and incorporate feedback even if requests for this arrive weeks or months after your MR submission
Please keep the change in a single MR as small as possible. If you want to contribute a large feature think very hard what the minimum viable change is. Can you split functionality? Can you only submit the backend/API code? Can you start with a very simple UI? The smaller a MR is the more likely it is it will be merged, after that you can send more MR's to enhance it.