FM / oauth1-client

/home/techb158/ileadtechnology.com/SSM/vendor/league/oauth1-client/

/home/techb158/ileadtechnology.com/SSM/vendor/league/oauth1-client

Name	Size	Mode	Actions
resources/	-	0755	rm
src/	-	0755	rm
tests/	-	0755	rm
.gitignore	40	0644	edit dl rm
.scrutinizer.yml	911	0644	edit dl rm
.travis.yml	669	0644	edit dl rm
composer.json	991	0644	edit dl rm
CONDUCT.md	2150	0644	edit dl rm
CONTRIBUTING.md	1200	0644	edit dl rm
LICENSE	1098	0644	edit dl rm
phpunit.xml	898	0644	edit dl rm
README.md	10722	0644	edit dl rm
rfc5849.txt	80786	0644	edit dl rm

Edit: /home/techb158/ileadtechnology.com/SSM/vendor/league/oauth1-client/CONTRIBUTING.md (1200B)

# Contributing

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

We accept contributions via Pull Requests on [Github](https://github.com/thephpleague/oauth1-client).

## Pull Requests

- **[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).

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

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

- **Consider our release cycle** - We try to follow semver. Randomly breaking public APIs is not an option.

- **Create topic branches** - Don't ask us to pull from your master branch.

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

- **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.

## Running Tests

``` bash
$ phpunit
```

**Happy coding**!

cmd: