Commit

26a894d

There’s a nice thread through these: all the little jobs around maintaining and releasing software. Keeping that straight gets messy when you have several projects going. Which one gets the most use in your own workflow?
Does lean-package-validator run in CI for you, or do you use it as a check before tagging a release? Curious where it fits in your workflow.

commit 26a894d

Both, but not yet consistently across all my PHP projects. I have it currently in an ill-named Composer script called pre-commit-check and also in the GitHub CI actions.