FM / laravel-backup

/home/techb158/ileadtechnology.com/vendor/spatie/laravel-backup/

/home/techb158/ileadtechnology.com/vendor/spatie/laravel-backup

Name	Size	Mode	Actions
.github/	-	0755	rm
config/	-	0755	rm
docs/	-	0755	rm
resources/	-	0755	rm
src/	-	0755	rm
CHANGELOG.md	16484	0644	edit dl rm
composer.json	1981	0644	edit dl rm
CONTRIBUTING.md	1336	0644	edit dl rm
LICENSE.md	1090	0644	edit dl rm
README.md	4289	0644	edit dl rm
UPGRADING.md	493	0644	edit dl rm

Edit: /home/techb158/ileadtechnology.com/vendor/spatie/laravel-backup/CONTRIBUTING.md (1336B)

# Contributing

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

We accept contributions via Pull Requests on [Github](https://github.com/spatie/laravel-backup).

## 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.md` 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**!

cmd: