summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames Lopez <james@gitlab.com>2019-02-27 16:53:51 +0000
committerJames Lopez <james@gitlab.com>2019-02-27 16:53:51 +0000
commitdb29496f60e1c2aac67de7db5102f2b9c0324b16 (patch)
tree58078a40f2f44b00f41a3ff9277f3ae805bbc7ca
parentb6e5fcb4aa114d917f025ffed09f0e5f6fb9f8ab (diff)
parent108d6731c7b43ca1a7ae62f846ca44dd263ec079 (diff)
downloadgitlab-ce-db29496f60e1c2aac67de7db5102f2b9c0324b16.tar.gz
Merge branch 'issue-template-feature-fix-ce' into 'master'
Fixed placeholder text in feature proposal issue template See merge request gitlab-org/gitlab-ce!25603
-rw-r--r--.gitlab/issue_templates/Feature proposal.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md
index 9c86dff835f..eef1e877ff2 100644
--- a/.gitlab/issue_templates/Feature proposal.md
+++ b/.gitlab/issue_templates/Feature proposal.md
@@ -39,7 +39,7 @@ Existing personas are: (copy relevant personas out of this comment, and delete a
### Permissions and Security
-What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
+<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? -->
### Documentation