CC-Tweaked/.github/pull_request_template.md

## A quick checklist
 - If there's a existing issue, please link to it. If not, provide fill out the same information you would in a normal issue - reproduction steps for bugs, rationale for use-case.
 - If you're working on CraftOS, try to write a few test cases so we can ensure everything continues to work in the future. Tests live in `src/test/resources/test-rom/spec` and can be run with `./gradlew check`.
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			`## A quick checklist`
			`- If there's a existing issue, please link to it. If not, provide fill out the same information you would in a normal issue - reproduction steps for bugs, rationale for use-case.`
			- If you're working on CraftOS, try to write a few test cases so we can ensure everything continues to work in the future. Tests live in `src/test/resources/test-rom/spec` and can be run with `./gradlew check`.