forgejo/.gitea/issue_template
Earl Warren 38e91fc76f
docs: rework the 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: screenshots` as they can be copy/pasted to the
  description when relevant. They are more important int the UI
  bug report template but not so much here.
* remove `id: git-ver` as it is almost never relevant. If it is, this
  can be included in the description but clutters the template most of
  the time.
* remove `id: os-ver` as it is redundant with what `id: run-info`
  requires.
* dev.next.forgejo.org is running the latest development branch
* link to dev.next.forgejo.org instead of next.forgejo.org
2024-07-15 15:49:44 +02:00
..
bug-report-ui.yaml issue_template: bug/new-report label 2024-03-22 10:11:35 +01:00
bug-report.yaml docs: rework the bug report template 2024-07-15 15:49:44 +02:00
config.yml [WORKFLOW] issues & pr templates (squash) allow empty issues 2024-02-05 15:08:04 +01:00
feature-request.yaml [WORKFLOW] yaml issue templates 2024-02-05 14:44:33 +01:00