Commit graph

18 commits

Author SHA1 Message Date
GitLab Bot
0a559c913e Add latest changes from gitlab-org/gitlab@master 2021-10-27 12:09:41 +00:00
GitLab Bot
da50206243 Add latest changes from gitlab-org/gitlab@master 2020-08-27 18:10:29 +00:00
GitLab Bot
2711c26bea Add latest changes from gitlab-org/gitlab@master 2020-03-24 00:09:24 +00:00
GitLab Bot
6f9edd1a4c Add latest changes from gitlab-org/gitlab@master 2019-09-23 15:06:32 +00:00
Brendan O'Leary 🐢
6745e12d9f Issue template grammar improvements 2019-05-17 18:09:16 +00:00
Carlos Soriano Sánchez
ef4c776bd3 Bug.md: Use html comments instead of asking to remove the notice
The issue template for bugs has a notice at the start that mentions to
search for duplicates before creating a new issue. Then the reporter
is asked to remove the notice once read, presumptively to avoid noise
in the actual issue.

Instead of that, we can make that part of the issue template an html
comment, so it won't be rendered in the final result. This avoids
the tedious task of removing that part of the notice.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/43580
2018-02-24 08:57:36 +00:00
Mark Fletcher
9d858d8a64 Mention both CE and EE issue trackers in description templates
[skip ci]
2017-06-21 08:30:48 +07:00
Mark Fletcher
9dd1ef182b Ask for an example project for bug reports
* Bugs reported in the GitLab Issue trackers should be reproducible
* Asking reporters to reproduce on GitLab.com is reasonable
  * It lets us know whether the issue still exists in latest
  * It ensures that the steps to reproduce are solid
  * It gives Developers a live example to work from
  * Reporter can verify the fix in the example project once shipped

[skip ci]
2017-05-31 18:39:37 +08:00
Mark Fletcher
a41a0c7642 Add summary lines for collapsed details in the bug report template
[skip ci]
2017-05-11 11:21:16 +08:00
Rémy Coutable
27f19a23ac
Add notice at the beginning of issue templates asking reporters to check for duplicates first
[ci skip]

Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-04-28 12:36:11 +02:00
Sean McGivern
4da39064ab Fix checks markup in bug template
Triple backticks aren't allowed inside <details> elements, so add an explicit
<pre> instead.
2017-04-27 11:59:43 +01:00
Z.J. van de Weg
00688e438c Let uses hide verbose output by default
[ci skip]
2017-04-12 14:01:20 +02:00
Rémy Coutable
6a874bc5dc
Try to disambiguate the Bug issue template
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-02-08 15:41:43 +01:00
Adam Niedzielski
a526e156a1 Encourage bug reporters to mention if they use GitLab.com [ci skip] 2016-12-06 16:08:53 +00:00
Clement Ho
e7f7df619d Rename behaviour to behavior in bug issue template for consistency 2016-09-01 22:01:02 -05:00
Mark Fletcher
7a83df749e Link to the issue templates in Contributing guide
Change to use a better title style

Add backticks to code segments

Spelling and Grammar
2016-08-25 15:48:08 +01:00
Mark Fletcher
b1add60648 Reflect template addition in the contributing guide
Adjust bug template to adhere to standard bug report format

* https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines
* Guidelines use the following format

- Summary
- Steps to Reproduce
- Expected Behaviour
- Actual Behaviour
2016-08-24 15:00:33 +01:00
Mark Fletcher
4b40767c0e First pass for community issue templates
* Include "Bug" template from the contribution guide
* Include "Feature Proposal" template from the contribution guide
2016-08-23 11:28:11 +01:00