CC-Tweaked/.github/ISSUE_TEMPLATE/feature_request.md

---
name: Feature request
about: Suggest an idea or improvement
labels: enhancement
---

<!--
## Before reporting
 - Search for the suggestion here. It's possible someone's suggested it before!
-->

## Useful information to include:
 - Explanation of how the feature/change should work.
 - Some rationale/use case for a feature. My general approach to designing new features is to ask yourself "what issue are we trying to solve" and _then_ "is this the best way to solve this issue?".
Add issue templates I'm not entirely a fan of massive templates, but there's been a couple of lacklustre issues recently, so it's probably good to formalise my guidelines. 2018-08-04 09:52:26 +00:00			`---`
			`name: Feature request`
			`about: Suggest an idea or improvement`
Automatically label issues created with templates 2019-05-25 13:53:36 +00:00			`labels: enhancement`
Add issue templates I'm not entirely a fan of massive templates, but there's been a couple of lacklustre issues recently, so it's probably good to formalise my guidelines. 2018-08-04 09:52:26 +00:00			`---`

			`<!--`
			`## Before reporting`
Update GitHub templates, removing CC repo links See #113 2019-02-18 23:35:50 +00:00			`- Search for the suggestion here. It's possible someone's suggested it before!`
Add issue templates I'm not entirely a fan of massive templates, but there's been a couple of lacklustre issues recently, so it's probably good to formalise my guidelines. 2018-08-04 09:52:26 +00:00			`-->`

			`## Useful information to include:`
Update GitHub templates, removing CC repo links See #113 2019-02-18 23:35:50 +00:00			`- Explanation of how the feature/change should work.`
A small bit of housekeeping - Add a link to discord and the forums. Oh goodness, I hope this doesn't count as making things official. I've had a couple of people email me with support requests, which is /fine/, but there's better channels for it! - Add a couple of PR templates - Ask people to write tests for CraftOS changes. This is a standard I'm trying to impose on myself, so seems reasonable to impose on everyone. Sorry! - Require same levels of explanation for PRs as we do for issues. - Try to expand on the feature request "rationale" section a little. Just trying to explan my process a little bit more. 2019-05-30 07:33:55 +00:00			`- Some rationale/use case for a feature. My general approach to designing new features is to ask yourself "what issue are we trying to solve" and _then_ "is this the best way to solve this issue?".`