forked from gitea/gitea
1
0
Fork 0
Commit Graph

34 Commits

Author SHA1 Message Date
silverwind d30410675b
Fix wording in issue template (#17176)
There was a typo `systemm` here. I opted to just remove the superfluos word altogether.
2021-09-29 13:03:44 +02:00
Gabriel a959ed99c2
Issue template form (#16349)
* 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>
2021-09-15 20:33:13 +03:00
Ikko Ashimine 5c7e2f47b7
Update pull_request_template.md (#15948)
Branch name
- master -> main
2021-05-22 10:46:33 -04:00
wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf c9a04cfdc8
Issue template addition: Are you using Gitea behind CloudFlare? (#14098)
* chore: are you using Gitea behind CloudFlare

since more often than not CF appears to serve stale cache and cause
troubles, I'd argue it might be helpful to ask about it in this here
issue template

* implement suggestion: change question to comment

* as per @techknowlogick's suggestion

* chore: edit comment

* implement @mrsdizzie's suggestion
* as the comment grows, rather span multiple lines
* Gitea --> gitea to match case used in the rest of the template

Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2021-02-18 12:28:07 +01:00
Kyle D 920c0bde2d
Kd/add bountysource (#14323)
* Add bountysource to Sponsors link

* Add badge to readme
2021-01-13 10:53:17 -05:00
6543 069acf6a21
Add FAQ link to Issue template (#14020) 2020-12-16 20:18:36 +01:00
6543 d02c3508e6
Config lock bot (#13624)
* config lock bot

* Update .github/lock.yml
2020-11-18 14:42:31 -05:00
zeripath 67b1a88e80
add more clarification to the issue-template.md (#13235)
Signed-off-by: Andrew Thornton <art27@cantab.net>

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-10-21 11:42:47 -04:00
mrsdizzie 4cc8697a65
Remove not relevant option from issue template (#13188)
Almost every use of "Not relevant" I see is the opposite -- it is relevant to have an example on try.gitea.io and often we can't do anything until the user provides one. Remove the not-relevant option so people have to decide yes/no if they are going to attempt to reproduce it which will hopefully encourage them to do so in simple cases. 

For actual not-relevant issues No should be a fine answer as well as it would be clear to us when you can't reproduce an example there.

Hopefully this will encourage more examples when people file issues which would lead to quicker fixes.
2020-10-17 23:46:59 +08:00
Antoine GIRARD eed361638a Improve stale message (#9920)
* Improve stale nessage

* Update .github/stale.yml

Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
2020-01-22 12:55:27 +02:00
Antoine GIRARD c39df04087 Display Github support button (#7343)
This need an option to be enabled on repo : https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository
2019-07-02 12:06:25 +02:00
John Olheiser 5c69e31c22 Add security note to issue template (#6281) 2019-03-08 13:15:46 -05:00
Antoine GIRARD 905e63f5b5 Force the PR close time to 60 days (#5770)
Like the comment that is posted.

Ex: https://github.com/go-gitea/gitea/pull/4749 is closed after 2 weeks and not 2 months
2019-01-19 12:21:03 -05:00
Antoine GIRARD 7cb1d8296d Create stale bot config (#5243) 2018-12-20 15:34:55 -05:00
Patrick G e90bbcaa52 Comment help text for issues (#2281) 2017-08-09 12:13:33 +08:00
Jonas Östanbäck a037cd81ff Add link to forum in issue template (#2070) 2017-06-28 09:33:37 +08:00
Jonas Östanbäck cc5484de10 Update links to Discord server 2017-06-11 19:42:08 +02:00
esell d87596aec4 Add MSSQL to issues template (#1171) 2017-03-10 09:31:57 +08:00
Patrick G aaf9adfbe8 Fix grammar (#1158) 2017-03-09 19:20:52 +08:00
Kim "BKC" Carlbäcker 669dad71f8 Add Screenshot-secion to IssueTemplate.md (#939)
For `UI`-bugs we usually require a Screenshot to debug it 😉
2017-02-17 08:58:01 +08:00
Bwko dc50c78f48 Replace pull request with issue at issue_template (#547) 2016-12-31 22:35:32 +08:00
Sandro Santilli 1831ee2d1d Update example install url from try.gogs.io to try.gitea.io (#385)
* Update example install url from try.gogs.io to try.gitea.io

* Ask if issue can be reproduced on try.gitea.io

* Link try.gitea.io to the README
2016-12-15 16:56:46 +08:00
Thomas Boerger 9628d4fb44
Unified GitHub templates accross all projects 2016-11-28 14:28:40 +01:00
Sandro Santilli 27f99a16a6 Review issue and pull templates, drop unused contributing file
The CONTRIBUTING.md from root dir will be used by github
2016-11-05 23:24:21 +01:00
Rémy Boulanouar 2d68bd1ef9 Change import reference to match gitea instead of gogs (#37) 2016-11-03 10:29:56 -02:00
rugk 28dc5bb566 Replace gogs.io http links with https version (#3386) 2016-08-05 17:35:40 -07:00
Unknwon 50422f1fc2 #3348 always use relative avatar link in the template 2016-08-05 12:12:54 -07:00
Unknwon f2884d8e31 Minor fix for pull request template [CI SKIP] 2016-07-28 10:54:52 +08:00
Unknwon 03ba257ad2 Update GitHub templates 2016-07-28 10:36:26 +08:00
Unknwon 5ec8ef0230 Update locales 2016-03-23 15:56:56 -04:00
Lubomir I. Ivanov 94f9ff1ac9 ISSUE_TEMPLATE: suggestion to test at try.gogs.io
I've noticed that a lot of issues cannot be reproduced on http://try.gogs.io,
which either hints about specific database type problems or
hints about bugs which are already solved in the newer version
(as http://try.gogs.io is usually a newer build).

This patch adds the suggestion to test the issue at http://try.gogs.io in
the Github "issue template". The user can answer: "Yes", "No", "Not relevant".

"Not relevant" is an option where testing on http://try.gogs.io makes no sense as
the bug is unrelated to the Web UI or is very specific in nature.
2016-03-02 20:12:14 +02:00
Unknwon d324500959 Prepare to release 2016-02-24 01:14:43 -05:00
Bart b91b35b565 Removed duplicate of paragraph 2016-02-21 16:02:00 +01:00
Unknwon 2fdf8fc938 Add issue and pull request template 2016-02-17 21:22:58 -05:00