FM / .github

/home/techb158/immovalet.com/vendor/spatie/laravel-newsletter/.github/

/home/techb158/immovalet.com/vendor/spatie/laravel-newsletter/.github

Name	Size	Mode	Actions
workflows/	-	0755	rm
CONTRIBUTING.md	1334	0644	edit dl rm
FUNDING.yml	49	0644	edit dl rm

Edit: /home/techb158/immovalet.com/vendor/spatie/laravel-newsletter/.github/CONTRIBUTING.md (1334B)

# Contributing

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

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

## 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
$ phpunit
```

**Happy coding**!

cmd: