Create contributing guide

Author: kna27

CONTRIBUTING.md

@@ -0,0 +1,19 @@
+# Contributing
+
+- Come up with an idea and put it on the spreadsheet
+- Create your challenge and create your yaml file, use the one from the [example chall](https://github.com/BCACTF/bcactf-3.0/blob/main/example/chall.yaml) as a guide
+- Create a branch, name it in the format of `category/chall-name`
+
+![Create Branch button](https://media.discordapp.net/attachments/829826615269785613/956348634000130069/unknown.png "Create Branch button")
+
+![Naming branch](https://media.discordapp.net/attachments/829826615269785613/956348738811609158/unknown.png "Naming branch")
+
+- Switch to your branch and publish it
+
+![Switch/Publish Branch](https://media.discordapp.net/attachments/829826615269785613/956349386655416431/unknown.png "Switch/Publish Branch")
+- Commit and push your chall, make sure to have no compiled binaries
+
+![New Pull Request](https://media.discordapp.net/attachments/829826615269785613/956382914000609380/unknown.png "New Pull Request")
+- Open a pull request, assign reviewers, labels, etc
+- We will review your challenge during club. Leave constructive criticism for your peers!
+- Do not merge your own challs, leave it to admin. We will not merge challs until they get at least two reviews.

README.md

@@ -6,3 +6,4 @@
 - Don't commit stuff like `node_modules`, compiled binaries, etc.
 - Include a solvepath
 - Send a PR and tag category leads for review
+- Look at [CONTRIBUTING.md](CONTRIBUTING.md) for more information