FM / vimeo-api

/home/techb158/ileadtechnology.com/vendor/vimeo/vimeo-api/

/home/techb158/ileadtechnology.com/vendor/vimeo/vimeo-api

Name	Size	Mode	Actions
src/	-	0755	rm
tests/	-	0755	rm
.gitattributes	23	0644	edit dl rm
.gitignore	31	0644	edit dl rm
.styleci.yml	297	0644	edit dl rm
.travis.yml	381	0644	edit dl rm
autoload.php	1004	0644	edit dl rm
CHANGELOG.md	6530	0644	edit dl rm
composer.json	994	0644	edit dl rm
composer.phar	2000535	0755	edit dl rm
CONTRIBUTING.md	1203	0644	edit dl rm
LICENSE	10174	0644	edit dl rm
phpunit.xml	630	0644	edit dl rm
psalm.xml	559	0644	edit dl rm
README.md	11096	0644	edit dl rm

Edit: /home/techb158/ileadtechnology.com/vendor/vimeo/vimeo-api/CONTRIBUTING.md (1203B)

Contributing
===

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

We accept contributions via Pull Requests on [Github](https://github.com/vimeo/vimeo.php).

## Pull Requests

- We try to follow the **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)**.

- **Document any change in behaviour** - Make sure the `README.md`, [wiki](https://github.com/vimeo/vimeo.php/wiki), and any other relevant documentation are kept up-to-date.

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

- **Create feature 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](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.

## Running Tests

```bash
$ composer test
```

**Happy coding**!

Contributing === Contributions are **welcome** and will be fully **credited**. We accept contributions via Pull Requests on [Github](https://github.com/vimeo/vimeo.php). ## Pull Requests - We try to follow the **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)**. - **Document any change in behaviour** - Make sure the `README.md`, [wiki](https://github.com/vimeo/vimeo.php/wiki), and any other relevant documentation are kept up-to-date. - **Consider our release cycle** - We try to follow [SemVer v2.0.0](http://semver.org/). Randomly breaking public APIs is not an option. - **Create feature 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](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting. ## Running Tests ```bash $ composer test ``` **Happy coding**!