We are using GitHub Actions as a continuous integration system.
For details, see workflows.
We are using friendsofphp/php-cs-fixer to automatically format the code.
Run
make fixto automatically format the code.
We are using phpstan/phpstan to statically analyze the code.
Run
make stanto run a static code analysis.
We are using phpunit/phpunit to drive the development.
Run
make testto run all the tests.
Run
maketo enforce coding standards, perform a static code analysis, and run tests!
💡 Run
make helpto display a list of available targets with corresponding descriptions.
This project uses Conventional Commits for automated version management and release notes generation.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
- feat: A new feature (triggers a minor version bump)
- fix: A bug fix (triggers a patch version bump)
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- chore: Changes to the build process or auxiliary tools and libraries
Add BREAKING CHANGE: in the footer or append ! after the type/scope to indicate breaking changes (triggers a major version bump).
feat: add support for PHP 8.4
fix: resolve memory leak in CSV parsing
docs: update installation instructions
feat!: drop support for PHP 7.4
feat(csv): add new export format
BREAKING CHANGE: PHP 7.4 is no longer supported
You can use scopes to specify which part of the codebase is affected:
csv: CSV-related functionalityholidays: Holiday calculation featuresmicroplate: Microplate handlingphpstan: PHPStan rulesscanner: Scanner-related featuressamplesheet: Sample sheet functionality