Request templates

Author: Alex Gurr

new_challenge_template.md

@@ -0,0 +1,35 @@
+## Challenge Name
+<!--- eg. CoinBee --> 
+
+## How Hard Do You Think The challenge Is?
+<!--- Tick ONE option --> 
+
+- [ ] Easy
+- [ ] Medium
+- [ ] Hard
+
+## Describe This Challenge
+<!--- A few sentences describing the challenge, how you use it and why you built it. -->
+
+<!--- eg. Chatter is based on a chat application and tests the user on sockets, socket.io, the ability to use hooks. The user is expected to make the app interactive with the chat server. --> 
+
+## Challenge Screenshots
+<!--- One desktop & one mobile -->
+
+## Challenge One Liner
+<!--- A small one liner for documentation --> 
+
+## Link To The Challenge Source Code
+<!--- A URL to your public repo with the partially completed source code (including requirements) -->
+
+## Link To The Solution Source Code
+<!--- A URL to your public repo with the fully completed source code -->
+
+## Challenge Checklist
+<!--- Ensure all items have been completed and tick the boxes --> 
+
+- [ ] My app is responsive
+- [ ] All core UI/UX has been built
+- [ ] I have built the solution to a good standard
+- [ ] I have added a README file with clear requirements and prerequisites
+- [ ] I have checked out the solution and made sure it runs

pull_request_template.md

@@ -0,0 +1,17 @@
+<!--- ** If you are submitting a new challenge, please use the [`new-challenge-template`](https://github.com/alexgurr/react-coding-challenges/blob/master/new_challenge_template.md) instead. ** -->
+
+## Proposed changes
+<!--- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.--> 
+
+## Types of changes
+
+<!--- What types of changes does your code introduce to react-coding-challenges? *Put a tick in the boxes that apply.* -->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation Update (if none of the other choices apply)
+
+## Further comments
+
+<!--- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc. -->