When opening new issues or commenting on existing issues on this repository please make sure discussions are related to concrete technical issues with the postcss-copy plugin.
Try to be friendly (we are not animals 🐒 or bad people 
) and explain correctly how we can reproduce your issue.
- Share the version of our plugin and PostCSS that you are using.
- Share your PostCSS configuration.
This document will guide you through the contribution process.
Fork the project on GitHub and check out your copy locally.
$ git clone git@github.com:username/postcss-copy.git
$ cd postcss-copy
$ git remote add upstream git://github.com/geut/postcss-copy.git
For developing new features and bug fixes, the master branch should be pulled
and built upon.
Create a feature branch and start hacking:
$ git checkout -b my-feature-branch -t origin/master
Bug fixes and features should come with tests. We use AVA to do that.
$ npm test
Make sure the linter is happy and that all tests pass. Please, do not submit patches that fail either check.
Make sure git knows your name and email address:
$ git config --global user.name "J. Random User"
$ git config --global user.email "j.random.user@example.com"
Writing good commit logs is important. A commit log should describe what changed and why.
$ git push origin my-feature-branch