diff options
| author | Nick Thomas <nick@gitlab.com> | 2018-10-17 18:06:49 +0100 |
|---|---|---|
| committer | Nick Thomas <nick@gitlab.com> | 2018-10-17 18:06:49 +0100 |
| commit | 0c13bffbdc121513ef8d586b0e912cfcd7ee3169 (patch) | |
| tree | ff3095824bd3c504f8385e0101d3579b7db4f4d2 /doc/development | |
| parent | 6b1820b5694e920323ada00cf36612f6343aceae (diff) | |
| download | gitlab-ce-0c13bffbdc121513ef8d586b0e912cfcd7ee3169.tar.gz | |
Maintainers should be involved in follow-up issues
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index ad7887b496d..dac2948dbca 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -351,7 +351,8 @@ The maintainer must always agree before an outstanding discussion is resolved in this manner, and will be the one to create the issue. The title and description should be of the same quality as those created [in the usual manner](#technical-and-ux-debt) - in particular, the issue title -**must not** begin with "Follow-up ...". +**must not** begin with `Follow-up`! The creating maintainer should also expect +to be involved in some capacity when work begins on the follow-up issue. ## Stewardship |