__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# Maintainers There aren't many rules for maintainers of Slim to remember; what we have is listed here. ## We don't merge our own PRs Our code is better if more than one set of eyes looks at it. Therefore we do not merge our own pull requests unless there is an exceptional circumstance. This helps to spot errors in the patch and also enables us to share information about the project around the maintainer team. ## PRs tagged `WIP` are not ready to be merged Sometimes it's helpful to collaborate on a patch before it's ready to be merged. We use the text `WIP` (for _Work in Progress_) in the title to mark these PRs. If a PR has `WIP` in its title, then it is not to be merged. The person who raised the PR will remove the `WIP` text when they are ready for a full review and merge. ## Assign a merged PR to a milestone By ensuring that all merged PRs are assigned to a milestone, we can easily find which PRs were in which release.
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| Slim | Folder | 0777 |
|
|
| CHANGELOG.md | File | 20.4 KB | 0777 |
|
| LICENSE.md | File | 1.04 KB | 0777 |
|
| MAINTAINERS.md | File | 946 B | 0777 |
|
| SECURITY.md | File | 286 B | 0777 |
|
| composer.json | File | 3.32 KB | 0777 |
|