diff options
| author | Warren Volz <warren@warrenvolz.com> | 2015-07-16 18:34:26 -0600 |
|---|---|---|
| committer | Warren Volz <warren@warrenvolz.com> | 2015-07-16 18:38:59 -0600 |
| commit | e25e70f9e284b3399c108c3d86358b0f599d928e (patch) | |
| tree | a63915e97987eabaa29dee191f1e2727588147d6 /CONTRIBUTING.md | |
| parent | 90f5c4d0a3c9d5e43e9a58ab0aa79c8b085c62d4 (diff) | |
| download | gitlab-ci-e25e70f9e284b3399c108c3d86358b0f599d928e.tar.gz | |
correct spelling of submission
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
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. |