__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# Coding Conventions * Use 4 spaces for indentation. * Code conforms to PEP8. Use pep8 or pycodestyle with their default settings to check for compliance. Consider using a pre-commit hook to prevent non-conforming code from entering the repo. * Avoid inline comments, prefer (short) block comments. * Add documentation strings to function if required. * Use type hints. * If you want, add yourself to the AUTHORS file. # Commit Conventions * Follow [conventional commit](https://www.conventionalcommits.org) message guidelines. * Scopes for commit messages are `etc`, `src` and file names from the root directory. Take a look at git log to get an impression. * You can ignore the 50 chars limit for the first line of a commit message and obey to a hard limit of 72 chars.
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| AUTHORS | File | 18 B | 0644 |
|
| CONTRIBUTING.md | File | 775 B | 0644 |
|
| LICENSE | File | 1.05 KB | 0644 |
|
| README.Debian | File | 347 B | 0644 |
|
| README.md.gz | File | 6.71 KB | 0644 |
|
| changelog.Debian.gz | File | 1.22 KB | 0644 |
|
| copyright | File | 1.38 KB | 0644 |
|