summaryrefslogtreecommitdiffstats
path: root/.forgejo/issue_template
diff options
context:
space:
mode:
authorDaniel Baumann <daniel@debian.org>2024-10-18 20:33:49 +0200
committerDaniel Baumann <daniel@debian.org>2024-10-18 20:33:49 +0200
commitdd136858f1ea40ad3c94191d647487fa4f31926c (patch)
tree58fec94a7b2a12510c9664b21793f1ed560c6518 /.forgejo/issue_template
parentInitial commit. (diff)
downloadforgejo-dd136858f1ea40ad3c94191d647487fa4f31926c.tar.xz
forgejo-dd136858f1ea40ad3c94191d647487fa4f31926c.zip
Adding upstream version 9.0.0.upstream/9.0.0upstreamdebian
Signed-off-by: Daniel Baumann <daniel@debian.org>
Diffstat (limited to '.forgejo/issue_template')
-rw-r--r--.forgejo/issue_template/bug-report-ui.yaml57
-rw-r--r--.forgejo/issue_template/bug-report.yaml72
-rw-r--r--.forgejo/issue_template/config.yml16
-rw-r--r--.forgejo/issue_template/feature-request.yaml31
4 files changed, 176 insertions, 0 deletions
diff --git a/.forgejo/issue_template/bug-report-ui.yaml b/.forgejo/issue_template/bug-report-ui.yaml
new file mode 100644
index 0000000..57d578b
--- /dev/null
+++ b/.forgejo/issue_template/bug-report-ui.yaml
@@ -0,0 +1,57 @@
+name: 🦋 Bug Report (web interface / frontend)
+description: Something doesn't look quite as it should? Report it here!
+title: "bug: "
+labels: ["bug/new-report", "forgejo/ui"]
+body:
+- type: markdown
+ attributes:
+ value: |
+ **NOTE: If your issue is a security concern, please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue.**
+- type: markdown
+ attributes:
+ value: |
+ - Please speak English, as this is the language all maintainers can speak and write.
+ - Be as clear and concise as possible. A very verbose report is harder to interpret in a concrete way.
+ - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
+ - Take a moment to [check that your issue hasn't been reported before](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78137).
+- type: dropdown
+ id: can-reproduce
+ attributes:
+ label: Can you reproduce the bug on the Forgejo test instance?
+ description: |
+ Please try reproducing your issue at https://dev.next.forgejo.org.
+ It is running the latest development branch and will confirm the problem is not already fixed.
+ If you can reproduce it, provide a URL in the description.
+ options:
+ - "Yes"
+ - "No"
+ validations:
+ required: true
+- type: textarea
+ id: description
+ attributes:
+ label: Description
+ description: |
+ Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see above).
+ If you think this is a JavaScript error, include a copy of the JavaScript console.
+ validations:
+ required: true
+- type: textarea
+ id: screenshots
+ attributes:
+ label: Screenshots
+ description: Please provide at least one screenshot showing the issue.
+ validations:
+ required: true
+- type: input
+ id: forgejo-ver
+ attributes:
+ label: Forgejo Version
+ description: Forgejo version (or commit reference) your instance is running
+- type: input
+ id: browser-ver
+ attributes:
+ label: Browser Version
+ description: The browser and version that you are using to access Forgejo
+ validations:
+ required: true
diff --git a/.forgejo/issue_template/bug-report.yaml b/.forgejo/issue_template/bug-report.yaml
new file mode 100644
index 0000000..6e9b116
--- /dev/null
+++ b/.forgejo/issue_template/bug-report.yaml
@@ -0,0 +1,72 @@
+name: 🐛 Bug Report (server / backend)
+description: Found something you weren't expecting? Report it here!
+title: "bug: "
+labels: bug/new-report
+body:
+- type: markdown
+ attributes:
+ value: |
+ **NOTE: If your issue is a security concern, please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue.**
+- type: markdown
+ attributes:
+ value: |
+ - Please speak English, as this is the language all maintainers can speak and write.
+ - Be as clear and concise as possible. A very verbose report is harder to interpret in a concrete way.
+ - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
+ - Take a moment to [check that your issue hasn't been reported before](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78137).
+- type: dropdown
+ id: can-reproduce
+ attributes:
+ label: Can you reproduce the bug on the Forgejo test instance?
+ description: |
+ Please try reproducing your issue at https://dev.next.forgejo.org.
+ It is running the latest development branch and will confirm the problem is not already fixed.
+ If you can reproduce it, provide a URL in the description.
+ options:
+ - "Yes"
+ - "No"
+ validations:
+ required: true
+- type: textarea
+ id: description
+ attributes:
+ label: Description
+ description: |
+ Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see above).
+ validations:
+ required: true
+- type: input
+ id: forgejo-ver
+ attributes:
+ label: Forgejo Version
+ description: Forgejo version (or commit reference) of your instance
+- type: textarea
+ id: run-info
+ attributes:
+ label: How are you running Forgejo?
+ description: |
+ Please include information on whether you built Forgejo yourself, used one of our downloads, or are using some other package.
+ Please also tell us how you are running Forgejo, e.g. if it is being run from a container, a command-line, systemd etc.
+ If you are using a package or systemd tell us what distribution you are using.
+ validations:
+ required: true
+- type: textarea
+ id: logs
+ attributes:
+ label: Logs
+ description: |
+ It's really important to provide pertinent logs. You must give us `DEBUG` level logs.
+ Please read https://forgejo.org/docs/latest/admin/logging-documentation/.
+ In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of `app.ini`.
+
+ Please copy and paste your logs here, with any sensitive information (e.g. API keys) removed/hidden.
+ You can wrap your logs in `<details>...</details>` tags so it doesn't take up too much space in the issue.
+- type: dropdown
+ id: database
+ attributes:
+ label: Database
+ description: What database system are you running?
+ options:
+ - SQLite
+ - PostgreSQL
+ - MySQL
diff --git a/.forgejo/issue_template/config.yml b/.forgejo/issue_template/config.yml
new file mode 100644
index 0000000..0e3caf9
--- /dev/null
+++ b/.forgejo/issue_template/config.yml
@@ -0,0 +1,16 @@
+contact_links:
+ - name: 🔓 Security Reports
+ url: mailto:security@forgejo.org
+ about: "Please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue."
+ - name: 💬 Matrix Chat Room
+ url: https://matrix.to/#/#forgejo-chat:matrix.org
+ about: Please ask questions and discuss configuration or deployment problems here.
+ - name: 💬 Matrix Space
+ url: https://matrix.to/#/#forgejo:matrix.org
+ about: A collection of Matrix rooms relating to Forgejo in addition to the main chat room.
+ - name: 📚 Documentation
+ url: https://forgejo.org/docs/latest/
+ about: Documentation about Forgejo.
+ - name: ❓ Frequently Asked Questions
+ url: https://forgejo.org/faq/
+ about: Please check if your question is mentioned here.
diff --git a/.forgejo/issue_template/feature-request.yaml b/.forgejo/issue_template/feature-request.yaml
new file mode 100644
index 0000000..0996680
--- /dev/null
+++ b/.forgejo/issue_template/feature-request.yaml
@@ -0,0 +1,31 @@
+name: 💡 Feature Request
+description: Got an idea for a feature that Forgejo doesn't have yet? Suggest it here!
+title: "feat: "
+labels: ["enhancement/feature"]
+body:
+- type: markdown
+ attributes:
+ value: |
+ - Please speak English, as this is the language all maintainers can speak and write.
+ - Be as clear and concise as possible. A very verbose request is harder to interpret in a concrete way.
+ - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
+ - Please make sure you are using the latest release of Forgejo and take a moment to [check that your feature hasn't already been suggested](https://codeberg.org/forgejo/forgejo/issues?q=&type=all&labels=78139).
+- type: textarea
+ id: needs-benefits
+ attributes:
+ label: Needs and benefits
+ description: As concisely as possible, describe the benefits your feature request will provide or the problems it will try to solve.
+ validations:
+ required: true
+- type: textarea
+ id: description
+ attributes:
+ label: Feature Description
+ description: As concisely as possible, describe the feature you would like to see added or the changes you would like to see made to Forgejo.
+ validations:
+ required: true
+- type: textarea
+ id: screenshots
+ attributes:
+ label: Screenshots
+ description: If you can, provide screenshots of an implementation on another site, e.g. GitHub.