# Contributing

**Icicle (icicle.io)** is an open-source project and welcomes contributions from the community. Below are the guidelines to contributing to Icicle.

- Icicle is released under the [MIT license](LICENSE). Any code or documentation you submit will be released under that license. If your contribution is substantial, we may ask that you sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement).
- Please submit any [issues](issues) or [pull requests](pulls) through GitHub.
- All code must be [PSR-1](http://www.php-fig.org/psr/psr-1/) and [PSR-2](http://www.php-fig.org/psr/psr-2/) compliant.
- Please see the [git-flow cheatsheet](http://danielkummer.github.com/git-flow-cheatsheet/) for a guide on how pull requests should be structured.
    - All pull requests for features or bugfixes should be made to the branch with the lowest version number possible. Changes will then be merged up to higher versions.
    - Please ensure that all tests pass before submitting a pull request. If you make changes to the code, please add, update, or remove unit tests as needed.
- If you'd like to implement a significant new feature, please contact us beforehand to avoid any duplication of effort.

# Contributing

**Icicle ([icicle.io](https://icicle.io))** is an open-source project and welcomes contributions from the community. Below are the guidelines to contributing to Icicle.

- Icicle is released under the [MIT license](LICENSE). Any code or documentation you submit will be released under that license. If your contribution is substantial, we may ask that you sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement).
- Please submit any [issues](https://github.com/icicleio/icicle/issues) or [pull requests](https://github.com/icicleio/icicle/pulls) through GitHub.
- All code must be [PSR-1](http://www.php-fig.org/psr/psr-1/) and [PSR-2](http://www.php-fig.org/psr/psr-2/) compliant.
- Please see the [git-flow cheatsheet](http://danielkummer.github.com/git-flow-cheatsheet/) for a guide on how pull requests should be structured.
    - All pull requests for features or bugfixes should be made to the branch with the lowest version number possible. Changes will then be merged up to higher versions.
    - Please ensure that all tests pass before submitting a pull request. If you make changes to the code, please add, update, or remove unit tests as needed.
- If you'd like to implement a significant new feature, please contact us beforehand to avoid any duplication of effort.

Fix issues and pulls links
Fix issues and pulls links
