omd:release-hygiene

Automating release hygiene checks involves scanning repositories for unwanted byproducts, verifying documentation synchronization, and evaluating NPM distribution decisions. You can execute a shell script via husky pre-commit hooks to validate release readiness and prevent unnecessary files from entering the codebase.

Release hygiene in version control is the practice of ensuring no unwanted byproducts are pushed to the repository and that documentation remains synchronized. It controls package releases by deciding whether deliverables belong in the NPM distribution or stay as local previews.

Yes, you need husky pre-commit hooks configured in your environment to run shell scripts for release checks. The automation relies on husky to trigger the shell scripting logic that scans for byproducts and validates documentation synchronization before code is committed.

To check documentation synchronization before a release, run an automated shell script that scans the project. This script verifies that all documentation accurately reflects the latest code changes and ensures dependencies are properly managed before NPM distribution.

The best way to remove unnecessary files and byproducts is to use an automated shell script integrated with husky pre-commit hooks. This approach scans the project during the commit process and automatically removes directories that should not be part of the release.

The script decides NPM package inclusion by assessing whether new deliverables should be distributed or remain as local previews. It evaluates the deliverables during the release hygiene check to control what is included in the final package distribution.