forgejo/.gitea/issue_template
Earl Warren fa263edcc3
docs: rework the user interface bug report template
* move `id: can-reproduce` to first position to give incentivize reproducers.
  If the description comes first, the person filing the bug report
  will describe the problem in plain English. It is better if the
  first thing they do, if at all possible, is to create a reproducer
  and provide a link.
* remove `id: os-ver` as it has never been relevant.
* do not require `id: forgejo-ver` because it does not matter that much
  as long as it can be reproduced on try.next.
* remove "If the error appears to relate to Forgejo the server" as it
  has never been relevant.
* require the description
2024-07-16 14:52:41 +02:00
..
bug-report-ui.yaml docs: rework the user interface bug report template 2024-07-16 14:52:41 +02:00
bug-report.yaml docs(issues): encourage the use of conventional commits 2024-07-16 14:33:21 +02:00
config.yml [WORKFLOW] issues & pr templates (squash) allow empty issues 2024-02-05 15:08:04 +01:00
feature-request.yaml docs(issues): encourage the use of conventional commits 2024-07-16 14:33:21 +02:00