__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# Contributing First of all, **thank you** for contributing! Here are a few rules to follow in order to ease code reviews and merging: - follow [PSR-1](http://www.php-fig.org/psr/1/) and [PSR-2](http://www.php-fig.org/psr/2/) - run the test suite - write (or update) unit tests when applicable - write documentation for new features - use [commit messages that make sense](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) One may ask you to [squash your commits](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) too. This is used to "clean" your pull request before merging it (we don't want commits such as `fix tests`, `fix 2`, `fix 3`, etc.). When creating your pull request on GitHub, please write a description which gives the context and/or explains why you are creating it.
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| src | Folder | 0777 |
|
|
| CONTRIBUTING.md | File | 834 B | 0777 |
|
| LICENSE | File | 1.05 KB | 0777 |
|
| README.md | File | 7.13 KB | 0777 |
|
| composer.json | File | 704 B | 0777 |
|
| readme_moodle.txt | File | 163 B | 0777 |
|