Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
0c13bffb
Commit
0c13bffb
authored
Oct 17, 2018
by
Nick Thomas
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Maintainers should be involved in follow-up issues
parent
6b1820b5
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
1 deletion
+2
-1
doc/development/contributing/issue_workflow.md
doc/development/contributing/issue_workflow.md
+2
-1
No files found.
doc/development/contributing/issue_workflow.md
View file @
0c13bffb
...
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment