Edit File by line

# Contributing

[0] Fix | Delete

[1] Fix | Delete

Contributions are **welcome** and will be fully **credited**.

[2] Fix | Delete

[3] Fix | Delete

We accept contributions via Pull Requests on [GitHub](https://github.com/noodlehaus/config).

[4] Fix | Delete

[5] Fix | Delete

[6] Fix | Delete

## Pull Requests

[7] Fix | Delete

[8] Fix | Delete

- **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)** - The easiest way to apply the conventions is to install [PHP Code Sniffer](http://pear.php.net/package/PHP_CodeSniffer).

[9] Fix | Delete

[10] Fix | Delete

- **Add tests!** - Your patch won't be accepted if it doesn't have tests.

[11] Fix | Delete

[12] Fix | Delete

- **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.

[13] Fix | Delete

[14] Fix | Delete

- **Consider our release cycle** - We try to follow [SemVer v2.0.0](http://semver.org/). Randomly breaking public APIs is not an option.

[15] Fix | Delete

[16] Fix | Delete

- **Use Git Flow** - Don't ask us to pull from your master branch. Set up [Git Flow](http://nvie.com/posts/a-successful-git-branching-model/) and create a new feature branch from `develop`

[17] Fix | Delete

[18] Fix | Delete

- **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.

[19] Fix | Delete

[20] Fix | Delete

- **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

[21] Fix | Delete

[22] Fix | Delete

[23] Fix | Delete

## Running Tests

[24] Fix | Delete

[25] Fix | Delete

``` bash

[26] Fix | Delete

$ phpunit

[27] Fix | Delete

```

[28] Fix | Delete

[29] Fix | Delete

[30] Fix | Delete

**Happy coding**!

[31] Fix | Delete

[32] Fix | Delete