* 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: os-ver` as it has never been relevant.
* do not require `id: forgejo-ver` because it does not matter that much
as long as it can be reproduced on try.next.
* remove "If the error appears to relate to Forgejo the server" as it
has never been relevant.
* require the description
* 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
(cherry picked from commit 9dd224f00c02151642523f31c98b819a2ea9b1b7)
(cherry picked from commit 710af007bccb62c65dd51ae46c77a297c0c58e43)
(cherry picked from commit 2ccd6e2bd60dbc829b98b75daef3b1360cd708e7)
(cherry picked from commit b90dc5fc4f90b7a916348378a089a9d54b23ce60)
(cherry picked from commit bf25d98a981800979073be008d254bfe0efe58bf)
(cherry picked from commit d7c71e598540ffe7586e99d0c9a8af53b564e5df)
[WORKFLOW] Add Forgejo Next and reproducing to issue template
(cherry picked from commit 17a3988fe09125755148380bc906f369b45b9764)
(cherry picked from commit 9ee5b3a619591143bb00bc26ec01fb350f2a0dfa)
(cherry picked from commit bebdd8d5f31cfab4e9fbe90d453305d264a99479)
(cherry picked from commit be7bb96d5c2303dbda5999ac20d32559e2085eed)
(cherry picked from commit 4ae659d63a095dacd01de798db83a8817a97dbf9)
(cherry picked from commit 82426f376d13d38c39364edfc58bf675cfd6918b)
(cherry picked from commit 1cb28e36712554961f16d912a443f86f535b3f42)
(cherry picked from commit c6a2db94c4b7861319fc63bc5e9304b2d4e61a22)
(cherry picked from commit 90d3eb2d1303dfd126c77721c1f3013b7da12db0)
(cherry picked from commit 3c3e656f582a0b3fdc8106ee7a30b4b3eb0b7c64)
(cherry picked from commit 54ece82417746fd725671309b68528db38796247)
(cherry picked from commit 55a042485a4c1d00ddddfb156c8db995af8b4819)
(cherry picked from commit 4e984aeba6e27fe86d11bebeffd5922bbdb7e7be)
(cherry picked from commit 52ea3f32b6f015e97ae84770d7254edcb1ff47d0)
(cherry picked from commit 00b0d0621efd3be8078d2dc9f0924f6ea16dd756)
(cherry picked from commit dc4acfa6db3cf9cce5cbf71cbda139541ca4b3d8)
(cherry picked from commit 0d26574fe3759057b66c43a64302a8f9c11ff17e)
(cherry picked from commit 81acdf5a84a9151b60977b5ca48018ea7ac739c3)
(cherry picked from commit bcb063e157a3fd9d58777f381b7fb894c4fb7149)
(cherry picked from commit 3e3bd36e6d526e53cdca3edd4da024efa351bf8e)
(cherry picked from commit 7767bafbffea48f1c1f06a7feefdbd72ba203496)
(cherry picked from commit c98e1afb4ccfaef14976b27304c07a3b5de5e6fb)
(cherry picked from commit 8ebc60b9495b6e7e4823f13880ae4582ee52281f)
(cherry picked from commit 59555d146e6a52aead047302a2affd5b73616e4a)
(cherry picked from commit 8ec25e8838b96aa4af135113663b8b4d28f5b8bf)
(cherry picked from commit 6e568c70d75a7aef7d64acc66991cae3cb26e378)
(cherry picked from commit 5a36052803d92ce51e3855889bb438e1ac0c7c7d)
(cherry picked from commit c7e6dc6b13b6d25f4c72a08f3e42fe931e309ec2)
(cherry picked from commit 005557f7ef4eb4ae14a8b454efab8b262c012e34)
(cherry picked from commit c643b2ef5879438d806cb93e244a1d8635408e3d)
(cherry picked from commit 8533627ee4ca96c43444f5962533a5a04ccfaddb)
(cherry picked from commit a9ce3d681cf2bb5c5e7d0dffb2635a5d43e65d76)
(cherry picked from commit e5efb10515b0dc37a5421f307eba6d9e86d68451)
(cherry picked from commit b0d00464ef242deb9b639729de201f72005f6af5)
(cherry picked from commit f54c25fa7d7b7752dcb46d0ec1138074256827af)
(cherry picked from commit b686249a4a41d35dfddb69087f42664c14fd3599)
(cherry picked from commit a55bc0abd37ed234eece6be333ceaff6fcec4626)
(cherry picked from commit bcb5e3480275799d5b6dc7af961a010fc1e5907c)
(cherry picked from commit e40a2d3e1542afba443cf671d84377d5eb0ef817)
(cherry picked from commit 412ef602c91b0c940947ba4274865c7bc9f70ae5)
(cherry picked from commit 536922186de8d43cf59202b2eec7df2c868eebef)
(cherry picked from commit 51c622012428b7ac6d5b50b884a6985ae86e22b5)
(cherry picked from commit 28d7612b3edbb0a7d911a0d1b257d0fe00600cfd)
(cherry picked from commit be3adcf77b1618dab693b2ae99e95f8a4ad7883e)
* 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>
