Update CONTRIBUTING.md

CONTRIBUTING.md

@@ -1,3 +1,5 @@
+# PLEASE STOP IGNORING THE ISSUE AND PR TEMPLATES
+
 
 ## How to Contribute 
 
@@ -31,7 +33,6 @@ Release branches take the form of `{semvar}-release`. For example:
 You can find the current release branch by checking out the [branches page](https://github.com/chriskiehl/Gooey/branches). 
 
 
-
 **Making Changes:**
 
 * Create a branch for your changes
@@ -71,12 +72,9 @@ Super Cool Person Above and Beyond Checklist Additions:
  - [ ] A sister commit in the [Examples Repo](https://github.com/chriskiehl/GooeyExamples) was created demonstrating your new feature 
 
 
+## Why is master the default branch when you don't want people submitting PRs to it? 
 
-
-
-
-
-
+In an ideal world, Github would give fine control over the semantics of what branches means what. I'd love to be able to say branch-xxx is for releases, branch-yyy is for staging, and branch-zzz for development. However, all we've got with tools of today is `default branch`. This default branch is what you get if you clone the library or pip install from source, and what you see when you land on the page. Personal preference is that this always give the healthiest view of the project possible. As such, the default branch tracks master, which houses the latest stable release, and mirrors what's in PyPi. 
 
 
 ## Code of Conduct
@@ -84,7 +82,6 @@ Super Cool Person Above and Beyond Checklist Additions:
 None. Use your best judgement. 
 
 
-
 ## Grumpy Stuff:
 
 * Please do not email me directly to ask why your PR hasn't been merged