| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Bug.md: Use html comments instead of asking to remove the notice | Carlos Soriano Sánchez | 2018-02-24 | 1 | -4/+2 |
| | | | | | | | | | | | | | 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 | ||||
| * | Simplify Feature Proposal templatesimplify-feature-proposals | Mark Pundsack | 2017-11-09 | 1 | -42/+1 |
| | | |||||
| * | a new feature checklist and more elaborate documentation requirements | Job van der Voort | 2017-06-21 | 1 | -6/+18 |
| | | |||||
| * | Mention both CE and EE issue trackers in description templates | Mark Fletcher | 2017-06-21 | 2 | -1/+14 |
| | | | | | [skip ci] | ||||
| * | Ask for an example project for bug reports | Mark Fletcher | 2017-05-31 | 1 | -0/+6 |
| | | | | | | | | | | | | * 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] | ||||
| * | Add summary lines for collapsed details in the bug report template | Mark Fletcher | 2017-05-11 | 1 | -0/+2 |
| | | | | | [skip ci] | ||||
| * | Add notice at the beginning of issue templates asking reporters to check for ↵ | Rémy Coutable | 2017-04-28 | 2 | -0/+31 |
| | | | | | | | | | duplicates first [ci skip] Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Fix checks markup in bug templatefix-issue-template-expansion | Sean McGivern | 2017-04-27 | 1 | -0/+4 |
| | | | | | | Triple backticks aren't allowed inside <details> elements, so add an explicit <pre> instead. | ||||
| * | Let uses hide verbose output by default | Z.J. van de Weg | 2017-04-12 | 1 | -0/+8 |
| | | | | | [ci skip] | ||||
| * | documentation blurb in issue template | Job van der Voort | 2017-03-17 | 1 | -0/+10 |
| | | |||||
| * | 27605 Add research proposal to issue templates27605-research-proposal-template | tauriedavis | 2017-02-16 | 1 | -0/+17 |
| | | |||||
| * | Try to disambiguate the Bug issue template27718-improve-bug-template | Rémy Coutable | 2017-02-08 | 1 | -12/+12 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Encourage bug reporters to mention if they use GitLab.com [ci skip] | Adam Niedzielski | 2016-12-06 | 1 | -0/+2 |
| | | |||||
| * | Rename behaviour to behavior in bug issue template for consistency | Clement Ho | 2016-09-01 | 1 | -1/+1 |
| | | |||||
| * | Link to the issue templates in Contributing guide | Mark Fletcher | 2016-08-25 | 2 | -17/+18 |
| | | | | | | | | | Change to use a better title style Add backticks to code segments Spelling and Grammar | ||||
| * | Reflect template addition in the contributing guide | Mark Fletcher | 2016-08-24 | 1 | -1/+5 |
| | | | | | | | | | | | | | 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 | ||||
| * | First pass for community issue templates | Mark Fletcher | 2016-08-23 | 2 | -0/+46 |
| * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide | |||||
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |