Merge pull request #195 from parkervcp/template_updates

Template updates

.github/ISSUE_TEMPLATE/bugs.md

@@ -5,7 +5,9 @@ about: Report an issue for an egg
 ---
 
 Please fill out the information bellow and remove from the line up
+If you just submit a bug with no info I will close out your bug.
 ---------------
+
 Panel Version: (version number)
 Daemon Version: (version number)
 Service: (minecraft/factorio/etc)

.github/ISSUE_TEMPLATE/issue_template.md

@@ -1,15 +0,0 @@
-Please fill out the information bellow and remove from the line up
----------------
-Panel Version: (version number)
-Daemon Version: (version number)
-New Service: (yes/no) (Is this a request for a new service?)
-Service: (minecraft/factorio/etc)
-Modified: (yes/no) (did you add or change things, this includes startup configs/install scripts/variables)
-
-Expected Behavior:
-
-Actual Behavior:
-
-Steps to Reproduce: (Step by step what to do to cause the issue)
-
-If this is a request for a new service then you can add info here like links to the site where the server files can be found. If it is a steamcmd game have you looked at the custom source engine service yet?

.github/ISSUE_TEMPLATE/request.md

@@ -5,7 +5,9 @@ about: Suggest a server to build an egg for
 ---
 
 Please fill out the information bellow and remove from the line up
+Please understand how Pterodactyl works when you are requesting an egg. (ie. docker-compose doesn't work for a pterodactyl server)
 ---------------
+
 Service: (Ex. minecraft/factorio/etc)
 
 Does this expand an already existing service: Y/N

.github/pull_request_template.md

@@ -2,6 +2,8 @@
 
 * [ ] Have you followed the guidelines in our Contributing document?
 * [ ] Have you checked to ensure there aren't other open [Pull Requests](../../pulls) for the same update/change?
+* [ ] Did you branch your changes and PR from that branch and not from your master branch?
+  * If not, why?:
 
 <!-- You can erase any parts of this template not applicable to your Pull Request. -->
 

CONTRIBUTING.md

@@ -11,6 +11,9 @@
 3. Try to stay in the stock containers.  
     If you need something in a container PR it to [my image repo](https://github.com/parkervcp/images) where I can review and pull up to the main repo.
 
+4. Don't be afraid to submit PR's to the egg repo.  
+    I dont bite. I will work with you on the egg and the required things to run it.
+
 ## Step 1.
 #### Be aware of the pterodactyl install process.
 
@@ -38,6 +41,6 @@ This is to maintain a clean repo that others can pull and be fully aware of what
 
 
 ## Step 3.
-#### Don't be afraid to submit PR's to the egg repo.
+#### Make a branch and do your work in there.
 
-I dont bite. I will work with you on the egg and the required things to run it.
+I have been getting messy PR's due to people always PRing from their master branch. Please make a branch and PR from there,