mirror of
https://github.com/go-gitea/gitea.git
synced 2024-11-30 12:14:51 +01:00
a959ed99c2
* Create issue template using new format This issue template has been based off of the current issue creation workflow defined in the ISSUE_TEMPLATE.md file This commit allows for that issue template (which is a legacy method of creating an issue) to be deleted * Delete old issue template file This commit deletes the old issue template file, as it is both legacy and replaced by ISSUE_TEMPLATE/issue.yaml * Adjust file upload and remove code of conduct checkbox * Block blank issue creation * Update feedback Removed most requirements Updated prompt to include instruction to state whether using try.gitea.io Added default value to Gitea version * Create Feature Request issue form * Update and rename issue.yaml to bug-report.yaml * Enable blank issue creation Co-authored-by: a1012112796 <1012112796@qq.com> * Update config.yaml * Remove default & placeholder from Gitea version * Create issue template in .gitea directory * Add relevant bug report message to feature request * Adjust name to remove banner There is a banner that tells you to create a config.yml when you already have a config.yaml Renaming the file stops this from occurring. * Add UI bug report form * Remove unnecessary question Co-authored-by: a1012112796 <1012112796@qq.com> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv>
63 lines
2.2 KiB
YAML
63 lines
2.2 KiB
YAML
name: Web Interface Bug Report
|
|
description: Something doesn't look quite as it should? Report it here!
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue.
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
1. Please speak English, this is the language all maintainers can speak and write.
|
|
2. Please ask questions or configuration/deploy problems on our Discord
|
|
server (https://discord.gg/gitea) or forum (https://discourse.gitea.io).
|
|
3. Please take a moment to check that your issue doesn't already exist.
|
|
4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq)
|
|
5. Please give all relevant information below for bug reports, because
|
|
incomplete details will be handled as an invalid report.
|
|
- type: input
|
|
id: gitea-ver
|
|
attributes:
|
|
label: Gitea Version
|
|
description: Gitea version (or commit reference) your instance is running
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
id: os-ver
|
|
attributes:
|
|
label: Operating System
|
|
description: The operating system you are using to access Gitea
|
|
- type: input
|
|
id: browser-ver
|
|
attributes:
|
|
label: Browser Version
|
|
description: The browser and version that you are using to access Gitea
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: can-reproduce
|
|
attributes:
|
|
label: Can you reproduce the bug on the Gitea demo site?
|
|
description: |
|
|
If so, please provide a URL in the Description field
|
|
URL of Gitea demo: https://try.gitea.io
|
|
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 using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services.
|
|
- type: textarea
|
|
id: screenshots
|
|
attributes:
|
|
label: Screenshots
|
|
description: Please provide at least 1 screenshot showing the issue.
|
|
validations:
|
|
required: true
|