setup-pre-commit

To set up pre-commit hooks for a multi-language repository, you need to detect each language surface and configure the appropriate ecosystem-specific tooling like Husky, pre-commit, or lefthook to gate commits with formatting and type-checking. This ensures code quality gates are automatically applied across all detected languages.

For Go or Rust projects, lefthook and cargo-husky are the respective pre-commit hook tools used to gate commits. They configure formatter and test gates specific to those ecosystems to ensure code quality before changes are committed.

Yes, in a multi-language repository you can apply Husky for Node and pre-commit for Python simultaneously. The setup detects the language surfaces and configures the respective per-ecosystem hook configurations independently.

The best way to automate linting and formatting before commits is by installing pre-commit hooks that detect your repository's ecosystem and apply formatter, type-checker, and test gates automatically prior to committing changes. This prevents unformatted code from entering your version control history.

Yes, setting up pre-commit hooks requires adding ecosystem-specific configuration files such as .husky/pre-commit, .pre-commit-config.yaml, or lefthook.yml, and ensuring that the generated hook scripts are executable.

Pre-commit hooks fail to run executable scripts when the generated hook files lack execute permissions. You must ensure ecosystem-specific configurations like .husky/pre-commit or Cargo.toml dev-dependencies are properly installed and marked as executable.