Sid Gifari File Manager Pro v10.0.3

📂 / (Root) / home / orkouolp / web / testing.orkobd / laravel / vendor / dflydev / dot-access-data / .github

📍 /home/orkouolp/web/testing.orkobd/laravel/vendor/dflydev/dot-access-data/.github

✏️ Editing: CONTRIBUTING.md Writable

# Contributing

Contributions are **welcome** and will be fully **credited**. We accept contributions via Pull Requests on [GitHub](https://github.com/dflydev/dflydev-dot-access-data).

## Pull Requests

- **[PSR-12 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-12-extended-coding-style-guide.md)** - The easiest way to apply the conventions is to run `./vendor/bin/phpcbf`.

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

- **Tests must pass** - All automated tests, including things like code style checks, but be passing before we'll consider merging the change.

- **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](https://semver.org/). Randomly breaking public APIs is not an option.

- **Create feature branches** - Don't ask us to pull from your default 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
$ composer test
```

**Happy coding**!

Sid Gifari File Manager Pro v10.0.3

📂 / (Root) / home / orkouolp / web / testing.orkobd / laravel / vendor / dflydev / dot-access-data / .github

📍 /home/orkouolp/web/testing.orkobd/laravel/vendor/dflydev/dot-access-data/.github

✏️ Editing: CONTRIBUTING.md Writable

# Contributing

Contributions are **welcome** and will be fully **credited**. We accept contributions via Pull Requests on [GitHub](https://github.com/dflydev/dflydev-dot-access-data).

## Pull Requests

- **[PSR-12 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-12-extended-coding-style-guide.md)** - The easiest way to apply the conventions is to run `./vendor/bin/phpcbf`.

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

- **Tests must pass** - All automated tests, including things like code style checks, but be passing before we'll consider merging the change.

- **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](https://semver.org/). Randomly breaking public APIs is not an option.

- **Create feature branches** - Don't ask us to pull from your default 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
$ composer test
```

**Happy coding**!