mirror of
https://github.com/go-gitea/gitea.git
synced 2024-12-18 11:03:04 +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>
43 lines
1.8 KiB
Markdown
43 lines
1.8 KiB
Markdown
<!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue -->
|
|
|
|
<!--
|
|
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.
|
|
-->
|
|
|
|
- Gitea version (or commit ref):
|
|
- Git version:
|
|
- Operating system:
|
|
<!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package -->
|
|
<!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. --->
|
|
<!-- If you are using a package or systemd tell us what distribution you are using -->
|
|
- Database (use `[x]`):
|
|
- [ ] PostgreSQL
|
|
- [ ] MySQL
|
|
- [ ] MSSQL
|
|
- [ ] SQLite
|
|
- Can you reproduce the bug at https://try.gitea.io:
|
|
- [ ] Yes (provide example URL)
|
|
- [ ] No
|
|
- Log gist:
|
|
<!-- It really is important to provide pertinent logs -->
|
|
<!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems -->
|
|
<!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini -->
|
|
|
|
## Description
|
|
<!-- 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. -->
|
|
|
|
...
|
|
|
|
|
|
## Screenshots
|
|
|
|
<!-- **If this issue involves the Web Interface, please include a screenshot** -->
|