2.2 KiB
How to Contribute
We'd love to accept your patches and contributions to this project.
Before you begin
Sign our Contributor License Agreement
Contributions to this project must be accompanied by a Contributor License Agreement (CLA). You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project.
If you or your current employer have already signed the Google CLA (even if it was for a different project), you probably don't need to do it again.
Visit https://cla.developers.google.com/ to see your current agreements or to sign a new one.
Review our Community Guidelines
This project follows Google's Open Source Community Guidelines.
Contribution process
Create an issue first
Before adding a new sample, create an issue first. Describe why this sample is needed and how you plan to implement it. Only once you've got the approval from one of the maintainers start working on a PR. Non trivial PRs without an approved issue will be rejected.
Code Reviews
All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.
Setting up your Environment
If you want to contribute to this repository, you need to first create your own fork. After forking chrome-extensions-samples to your own Github account, run the following steps to get started:
# clone your fork to your local machine
git clone https://github.com/your-fork/chrome-extensions-samples.git
cd chrome-extensions-samples
# install dependencies
npm install
Writing a README
All new code samples or samples updated from Manifest V2 should include a README file. Please copy the provided template into your sample's folder and follow the instructions therein.