gtk/.gitlab/issue_templates/Bug.md

<!--
  Please, read the CONTRIBUTING.md guide on how to file a new issue.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/master/CONTRIBUTING.md
-->
## Steps to reproduce
<!--
  Please, explain the sequence of actions necessary to reproduce the
  bug
-->

 1. ...
 2. ...
 3. ...

<!--
  You should try and reproduce with the demos applications available
  under the `demos` directory, or the test programs in the `tests` directory.
  Alternatively, please attach a *small and self-contained* example
  *written in C* that exhibits the issue.
-->

## Current behavior
<!--
  Please describe the current behaviour
-->

## Expected outcome
<!--
  Please describe the expected outcome
-->

## Version information
<!--
 - Which version of GTK you are using
 - What operating system and version
  - For Linux, which distribution
 - If you built GTK yourself, the list of options used to configure the build
-->

## Additional information
<!--
 - Screenshots or screen recordings are useful for visual errors
  - Attaching a screenshot or a video without explaining the current
    behavior and the actions necessary to reproduce the bug will lead
    to the bug being closed
 - Please report any warning or message printed on the terminal
-->
Add more directions to the issue templates Let's hope people read them. 2021-01-15 14:20:09 +00:00			`<!--`
			`Please, read the CONTRIBUTING.md guide on how to file a new issue.`

			`https://gitlab.gnome.org/GNOME/gtk/-/blob/master/CONTRIBUTING.md`
			`-->`
Add a template for bug reports GitLab issues can use templates to guide users when filing new bug reports; we should take advantage of this feature. 2018-03-21 00:59:06 +00:00			`## Steps to reproduce`
Add more directions to the issue templates Let's hope people read them. 2021-01-15 14:20:09 +00:00			`<!--`
			`Please, explain the sequence of actions necessary to reproduce the`
			`bug`
			`-->`
Add a template for bug reports GitLab issues can use templates to guide users when filing new bug reports; we should take advantage of this feature. 2018-03-21 00:59:06 +00:00
			`1. ...`
			`2. ...`
			`3. ...`

			`<!--`
			`You should try and reproduce with the demos applications available`
			under the `demos` directory, or the test programs in the `tests` directory.
issue templates: reproducers should be written in C I don't want to install a new set of bindings every time someone attaches a reproducer to a bug. I also don't want to rewrite sait reproducer in C every time just to eliminate the possibility of broken bindings. 2019-05-17 06:55:40 +00:00			`Alternatively, please attach a small and self-contained example`
			`written in C that exhibits the issue.`
Add a template for bug reports GitLab issues can use templates to guide users when filing new bug reports; we should take advantage of this feature. 2018-03-21 00:59:06 +00:00			`-->`

			`## Current behavior`
			`<!--`
			`Please describe the current behaviour`
			`-->`

			`## Expected outcome`
			`<!--`
			`Please describe the expected outcome`
			`-->`

Reduce the header level in the bug template Make version and additional information headers use h2, like everything else. 2018-03-21 11:49:24 +00:00			`## Version information`
Add a template for bug reports GitLab issues can use templates to guide users when filing new bug reports; we should take advantage of this feature. 2018-03-21 00:59:06 +00:00			`<!--`
gitlab templates: Its just GTK now More plus purging. 2019-02-24 15:44:15 +00:00			`- Which version of GTK you are using`
Add an issue template for crashers Better to have separate templates than a large, "choose your own adventure" one. 2018-04-17 08:38:11 +00:00			`- What operating system and version`
			`- For Linux, which distribution`
Remove two more plusses 2019-04-17 01:27:17 +00:00			`- If you built GTK yourself, the list of options used to configure the build`
Add a template for bug reports GitLab issues can use templates to guide users when filing new bug reports; we should take advantage of this feature. 2018-03-21 00:59:06 +00:00			`-->`

Reduce the header level in the bug template Make version and additional information headers use h2, like everything else. 2018-03-21 11:49:24 +00:00			`## Additional information`
Add a template for bug reports GitLab issues can use templates to guide users when filing new bug reports; we should take advantage of this feature. 2018-03-21 00:59:06 +00:00			`<!--`
Add an issue template for crashers Better to have separate templates than a large, "choose your own adventure" one. 2018-04-17 08:38:11 +00:00			`- Screenshots or screen recordings are useful for visual errors`
Add more directions to the issue templates Let's hope people read them. 2021-01-15 14:20:09 +00:00			`- Attaching a screenshot or a video without explaining the current`
			`behavior and the actions necessary to reproduce the bug will lead`
			`to the bug being closed`
Add an issue template for crashers Better to have separate templates than a large, "choose your own adventure" one. 2018-04-17 08:38:11 +00:00			`- Please report any warning or message printed on the terminal`
			`-->`