We love your input! 🚀 We 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.
- Becoming a maintainer.
We use github to host code, track issues and feature requests, and accept pull requests.
We Use Github Flow, So All Code Changes Happen Through Pull Requests
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch from
main. - Add tests if you've added code that should be tested.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- 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.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
This is an example of a bug report, and I think it's a good model. Here's another example from Craig Hockenberry, an app developer greatly respected in the community.
Great Bug Reports tend to have:
- A quick summary and/or background.
- Steps to reproduce:
- Be specific!
- Give sample code if you can. This stackoverflow question includes sample code that anyone with a base R setup can run to reproduce the error.
- 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).
People love thorough bug reports. I'm not even kidding.
We use shfmt to format our shell scripts. The easiest way to use shfmt is through the bash-beautify or shell-format VS Code extensions.
By contributing, you agree that your contributions will be licensed under its MIT License.
This document was adapted from the open-source contribution guidelines for Facebook's Draft.