oppi.li / perf-test
loading up the forgejo repo on tangled to test page performance
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Merge pull request 'docs: rework the bug report template' (#4514) from earl-warren/forgejo:wip-bug-report-template into forgejo

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4514
Reviewed-by: Victoria <efertone@noreply.codeberg.org>
Reviewed-by: jean-daricade <jean-daricade@noreply.codeberg.org>

Earl Warren e98c9d2a 74206dc0

+21 -38
+21 -38
.gitea/issue_template/bug-report.yaml
··· 13 13 - Please speak English, as this is the language all maintainers can speak and write. 14 14 - Be as clear and concise as possible. A very verbose report is harder to interpret in a concrete way. 15 15 - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct). 16 - - Please make sure you are using the latest release of Forgejo and take a moment to [check that your issue hasn't been reported before](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78137). 17 - - Please give all relevant information below for bug reports, as incomplete details may result in the issue not being considered. 16 + - Take a moment to [check that your issue hasn't been reported before](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78137). 17 + - type: dropdown 18 + id: can-reproduce 19 + attributes: 20 + label: Can you reproduce the bug on the Forgejo test instance? 21 + description: | 22 + Please try reproducing your issue at https://dev.next.forgejo.org. 23 + It is running the latest development branch and will confirm the problem is not already fixed. 24 + If you can reproduce it, provide a URL in the description. 25 + options: 26 + - "Yes" 27 + - "No" 28 + validations: 29 + required: true 18 30 - type: textarea 19 31 id: description 20 32 attributes: 21 33 label: Description 22 34 description: | 23 - Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below). 35 + Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see above). 24 36 validations: 25 37 required: true 26 38 - type: input ··· 28 40 attributes: 29 41 label: Forgejo Version 30 42 description: Forgejo version (or commit reference) of your instance 31 - validations: 32 - required: true 33 - - type: dropdown 34 - id: can-reproduce 43 + - type: textarea 44 + id: run-info 35 45 attributes: 36 - label: Can you reproduce the bug on Forgejo Next? 46 + label: How are you running Forgejo? 37 47 description: | 38 - Please try reproducing your issue at [Forgejo Next](https://next.forgejo.org). 39 - If you can reproduce it, please provide a URL in the Description field. 40 - options: 41 - - "Yes" 42 - - "No" 48 + Please include information on whether you built Forgejo yourself, used one of our downloads, or are using some other package. 49 + Please also tell us how you are running Forgejo, e.g. if it is being run from a container, a command-line, systemd etc. 50 + If you are using a package or systemd tell us what distribution you are using. 43 51 validations: 44 52 required: true 45 53 - type: textarea ··· 53 61 54 62 Please copy and paste your logs here, with any sensitive information (e.g. API keys) removed/hidden. 55 63 You can wrap your logs in `<details>...</details>` tags so it doesn't take up too much space in the issue. 56 - - type: textarea 57 - id: screenshots 58 - attributes: 59 - label: Screenshots 60 - description: If this issue involves the Web Interface, please provide one or more screenshots 61 - - type: input 62 - id: git-ver 63 - attributes: 64 - label: Git Version 65 - description: The version of git running on the server 66 - - type: input 67 - id: os-ver 68 - attributes: 69 - label: Operating System 70 - description: The operating system you are using to run Forgejo 71 - - type: textarea 72 - id: run-info 73 - attributes: 74 - label: How are you running Forgejo? 75 - description: | 76 - Please include information on whether you built Forgejo yourself, used one of our downloads, or are using some other package. 77 - Please also tell us how you are running Forgejo, e.g. if it is being run from docker, a command-line, systemd etc. 78 - If you are using a package or systemd tell us what distribution you are using. 79 - validations: 80 - required: true 81 64 - type: dropdown 82 65 id: database 83 66 attributes: