summaryrefslogtreecommitdiff
path: root/.gitlab
Commit message (Collapse)AuthorAgeFilesLines
* Simplify the DB changes checklistsimplify-db-changes-templateYorick Peterse2017-11-231-37/+9
| | | | | | | This removes some somewhat redundant checkboxes from the template and rephrases the introduction now that those settings are in GDK. [ci skip]
* Simplify Feature Proposal templatesimplify-feature-proposalsMark Pundsack2017-11-091-42/+1
|
* Add .gitlab/route-map.ymlRémy Coutable2017-10-301-0/+3
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Added a template for database changesYorick Peterse2017-08-101-0/+73
| | | | | | | | | This template includes a rather large (but fairly easy to follow) checklist. This checklist should hopefully take away quite a bit of work from database specialists by requiring authors to provide all the necessary info. [ci skip]
* a new feature checklist and more elaborate documentation requirementsJob van der Voort2017-06-211-6/+18
|
* Mention both CE and EE issue trackers in description templatesMark Fletcher2017-06-212-1/+14
| | | | [skip ci]
* Ask for an example project for bug reportsMark Fletcher2017-05-311-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 templateMark Fletcher2017-05-111-0/+2
| | | | [skip ci]
* Add notice at the beginning of issue templates asking reporters to check for ↵Rémy Coutable2017-04-282-0/+31
| | | | | | | | duplicates first [ci skip] Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix checks markup in bug templatefix-issue-template-expansionSean McGivern2017-04-271-0/+4
| | | | | Triple backticks aren't allowed inside <details> elements, so add an explicit <pre> instead.
* Let uses hide verbose output by defaultZ.J. van de Weg2017-04-121-0/+8
| | | | [ci skip]
* documentation blurb in issue templateJob van der Voort2017-03-171-0/+10
|
* 27605 Add research proposal to issue templates27605-research-proposal-templatetauriedavis2017-02-161-0/+17
|
* Try to disambiguate the Bug issue template27718-improve-bug-templateRémy Coutable2017-02-081-12/+12
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Encourage bug reporters to mention if they use GitLab.com [ci skip]Adam Niedzielski2016-12-061-0/+2
|
* remove a period that can be annoyingremove-periodDe Wet Blomerus2016-10-141-1/+1
|
* Rename behaviour to behavior in bug issue template for consistencyClement Ho2016-09-011-1/+1
|
* Add MR Documentation description templateAchilleas Pipinellis2016-09-011-0/+14
|
* Link to the issue templates in Contributing guideMark Fletcher2016-08-252-17/+18
| | | | | | | | Change to use a better title style Add backticks to code segments Spelling and Grammar
* Reflect template addition in the contributing guideMark Fletcher2016-08-241-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 templatesMark Fletcher2016-08-232-0/+46
* Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide