Update CONTRIBUTING.md

Author: UltiRequiem

CONTRIBUTING.md

@@ -1 +1,36 @@
+# Contributing
+I love your input!I want to make contributing to this project as easy and transparent as possible, whether it's:
 
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+
+## I Develop with Github
+I use github to host code, to track issues and feature requests, as well as accept pull requests.
+
+### I Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `master`.
+2. If you've added code that should be tested, add tests.
+3. Ensure the test suite passes.
+4. Make sure your code lints.
+5. Issue that pull request!
+
+## Report bugs using Github's [issues](https://github.com/EliazBobadilla/C-UltiSnippets-VSCode-Extension/issues)
+I use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/EliazBobadilla/C-UltiSnippets-VSCode-Extension/issues) it's that easy!
+
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+## Any contributions you make will be under the MIT Software License
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to send me a message if that's a concern.