|
| 1 | +# Contributing to @vuestorefront/redis-driver |
| 2 | +We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's: |
| 3 | + |
| 4 | +- Reporting a bug |
| 5 | +- Discussing the current state of the code |
| 6 | +- Submitting a fix |
| 7 | +- Proposing new features |
| 8 | +- Becoming a maintainer |
| 9 | + |
| 10 | +## We Develop with Github |
| 11 | +We use github to host code, to track issues and feature requests, as well as accept pull requests. |
| 12 | + |
| 13 | +## We Use [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow), So All Code Changes Happen Through Pull Requests |
| 14 | +Pull requests are the best way to propose changes to the codebase (we use [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)). We actively welcome your pull requests: |
| 15 | + |
| 16 | +1. Fork the repo and create your branch from `develop`. |
| 17 | +2. If you've added code that should be tested, add tests. |
| 18 | +3. If you've changed APIs, update the documentation. |
| 19 | +4. Ensure the test suite passes. |
| 20 | +5. Make sure your code lints. |
| 21 | +6. Issue that pull request! |
| 22 | + |
| 23 | +## Any contributions you make will be under the MIT Software License |
| 24 | +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 contact the maintainers if that's a concern. |
| 25 | + |
| 26 | +## Report bugs using Github's [issues](https://github.com/vuestorefront/redis-driver/issues) |
| 27 | +We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/vuestorefront/redis-driver/issues/new); it's that easy! |
| 28 | + |
| 29 | +## Write bug reports with detail, background, and sample code |
| 30 | +**Great Bug Reports** tend to have: |
| 31 | + |
| 32 | +- A quick summary and/or background |
| 33 | +- Steps to reproduce |
| 34 | + - Be specific! |
| 35 | + - Give sample code if you can. |
| 36 | +- What you expected would happen |
| 37 | +- What actually happens |
| 38 | +- The environment you're running the application |
| 39 | +- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work) |
| 40 | + |
| 41 | +People *love* thorough bug reports. I'm not even kidding. |
| 42 | + |
| 43 | +## Use a Consistent Coding Style |
| 44 | +I'm again borrowing these from [AirBnB's Code Style](https://github.com/airbnb/javascript) |
| 45 | + |
| 46 | +* 2 spaces for indentation rather than tabs |
| 47 | +* You can try running `npm run lint` for style unification |
| 48 | + |
| 49 | +## License |
| 50 | +By contributing, you agree that your contributions will be licensed under its MIT License. |
0 commit comments