| name | dev-workflow |
|---|---|
| description | Use when running Composer, CI, or PRs to master/next — installs, tests, and branch policy for this repo. |
- Installing dependencies or running the test suite locally
- Understanding what GitHub Actions run on push/PR
- Opening or reviewing a PR and matching branch expectations
- From the repo root:
composer install(usecomposer install --ignore-platform-reqsonly if you must match CI’s relaxed install; see.github/workflows/ci.yml). - Run tests:
composer test(runs PHPUnit as defined incomposer.json).
- Check:
composer check-style(PHPCS onsrcandtests). - Autofix where supported:
composer fix-style(PHPCBF).
ci.yml:composer validate, cache +composer install, thencomposer run-script test.- Lint is not currently enforced in that workflow; still run
check-stylebefore pushing.
check-branch.yml: PRs intomastermust use branchnextas the head branch (automation comments and fails otherwise).- Prefer feature branches (not your fork’s default branch name as the only source) per
CONTRIBUTING.md.
- Project follows SemVer per
CONTRIBUTING.md; public API changes belong in changelog/release notes as the maintainers require.