How to Contribute
Third-party patches are essential for keeping open-source software great. In the spirit of keeping it possible to contribute changes that get things working in your environment, here are a few guidelines that contributors should follow. As Nicolas Gallagher put it in the normalize.css contributing guidelines:
Following these guidelines helps to communicate that you respect the time of the developers managing and developing […]. In return, they should reciprocate that respect in addressing your issue or assessing your patches and features.
- Make sure you have a GitHub account.
- Please ask anyone of the users in the repository’s CODEOWNERS file before making significant changes. We’d hate for you to put in a lot of work for something that doesn’t align with the vision of the project.
- Search on Github within the repository for the issue or Pull Request. This means you have to read through the issue(s) in order to determine if your particular issue has already been created. Don’t forget to look through the closed ones as well.
- If the issue has not been fixed then try to reproduce the issue in a fresh clone of the repository off the
mainbranch. Read on how to set up your environment. - Create a reduced test case as outlined by Chris Coyier of CSS Tricks. Link to the Code Pen, JS Bin, or whatever you use, as long as its publicly accessible.
- Read our branching strategy, commit conventions for tips on how to contribute. We won’t accept any pull request that doesn’t adhere, so be forewarned.
If this seems like a lot or you aren’t able to do all this setup, you might also be able to edit the files directly without having to do any of this setup. Yes, even code.
Ways to Contribute
We look forward to your contributions. ✨