diff options
author | Douwe Maan <douwe@gitlab.com> | 2016-03-18 15:11:41 +0300 |
---|---|---|
committer | Douwe Maan <douwe@gitlab.com> | 2016-03-18 15:11:41 +0300 |
commit | 691d5db5986f8f57d187d3da19c69ef92087fe75 (patch) | |
tree | 338860ac3e84ba91c27faa800abbf0d63bf263f7 | |
parent | efa1bc372fbfbf0503b7452e17c7034c512e19bc (diff) |
Change capitalization
-rw-r--r-- | CONTRIBUTING.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5d4aa61fb12..511336f384c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -246,7 +246,7 @@ addressed. ### Technical debt In order to track things that can be improved in GitLab's codebase, we created -the ~"Technical debt" label in [GitLab's issue tracker][ce-tracker]. +the ~"technical debt" label in [GitLab's issue tracker][ce-tracker]. This label should be added to issues that describe things that can be improved, shortcuts that have been taken, code that needs refactoring, features that need @@ -255,14 +255,14 @@ high velocity of development. Everyone can create an issue, though you may need to ask for adding a specific label, if you do not have permissions to do it by yourself. Additional labels -can be combined with the `Technical debt` label, to make it easier to schedule +can be combined with the `technical debt` label, to make it easier to schedule the improvements for a release. -Issues tagged with the `Technical debt` label have the same priority like issues +Issues tagged with the `technical debt` label have the same priority like issues that describe a new feature to be introduced in GitLab, and should be scheduled for a release by the appropriate person. -Make sure to mention the merge request that the `Technical debt` issue is +Make sure to mention the merge request that the `technical debt` issue is associated with in the description of the issue. ## Merge requests |