We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a
bug
orissue
- Discussing the current state of the code
- Submitting a fix of
bug
orissue
- Proposing new
features
to be added - Becoming a
maintainer
orcontributor
with us
We use GitHub
to host code, track issues
, and feature requests
, as well as accept pull requests
.
Here's how you can make a pull request
(PR):
- Fork the repo and create your branch from
master
. - If you've added code that should be tested, add tests.
- Ensure the test suite passes.
- Make sure your code lines.
- Issue that pull request!
In short, when you submit code changes, your submissions are understood to be under the same MIT
License that covers the project. Feel free to contact the maintainers
if that's a concern.
We use GitHub issues
to track public bugs
. Report a bug
by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and background
- Steps to reproduce
- Be
specific
! - Give
sample code
if you can.
- Be
- What you expected would happen
- What happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports.
- You can check out the
SCSS Guidelines
for coding conventions. - Ensure your code passes the project's linting standards.
By contributing, you agree that your contributions will be licensed under its MIT
License.