5 Commits (62f2d717b7e04565c5ff260746e43ed64a87b0e0)

Author	SHA1	Message	Date
silverwind	3c0c279658	Add `yamllint` (#26965) ... So that https://github.com/go-gitea/gitea/pull/26964 does not happen again. Merge this after that PR. Config is based on [node's](https://github.com/nodejs/node/blob/main/.yamllint.yaml). --------- Co-authored-by: techknowlogick <techknowlogick@gitea.com>	1 year ago
Lunny Xiao	476b9d1589	Use docs.gitea.com instead of docs.gitea.io (#26739)	1 year ago
delvh	bfe2e3d562	Reorder issue templates and automatically add labels (#18875) ... * Reorder bug-report.yaml * Add bug label on bug-report.yaml * Add feature label on feature-request.yaml * Reorder ui.bug-report.yaml * Apply suggestions Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: zeripath <art27@cantab.net>	3 years ago
zeripath	6d11a31aef	Make the proformas clearer that we need DEBUG logs (#18700) ... It is ridiculous how few of our bug reporter are giving us DEBUG level logs. This has to change and I think the proforma is not making it clear enough that they have to give us these logs. This PR changes the issue proformas to tell people to give us these logs. Signed-off-by: Andrew Thornton <art27@cantab.net>	3 years ago
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>	3 years ago