diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-10 21:10:45 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-10 21:10:45 +0000 |
| commit | 98692a8dd50b5325d3f846c70ec804d0a9442f55 (patch) | |
| tree | 7ec8d2d762f56e1124a846194b078c062f5de8a2 /doc/development | |
| parent | ed5add1c2f001c9bd54e664b32f212de172eca6a (diff) | |
| download | gitlab-ce-98692a8dd50b5325d3f846c70ec804d0a9442f55.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index a4c55cdbd1b..5df357eee9e 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -449,7 +449,7 @@ It's common to discover technical debt during development of a new feature. In the spirit of "minimum viable change", resolution is often deferred to a follow-up issue. However, this cannot be used as an excuse to merge poor-quality code that would otherwise not pass review, or to overlook trivial matters that -don't deserve the be scheduled independently, and would be best resolved in the +don't deserve to be scheduled independently, and would be best resolved in the original merge request - or not tracked at all! The overheads of scheduling, and rate of change in the GitLab codebase, mean |