2 Commits (fbd4eaceed801e7400ed04a9dadedaf3a25dccb9)

Author	SHA1	Message	Date
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
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