Build-driver selection

Updated Jul 21, 2026

The hook runs repository-native quality targets through a selected build driver. Automatic selection uses this order:

  1. Use Netsuke when Netsukefile exists and netsuke is available on PATH.
  2. Otherwise use Make when Makefile exists and make is available on PATH.
  3. When neither Netsukefile nor Makefile exists, skip repository quality targets and continue with branch-state gates.

Automatic mode still reports an error when manifests are present but no usable build driver remains, such as when the only manifest's matching executable is missing.

Set POST_TURN_BUILD_DRIVER to override automatic selection:

  • auto keeps the default behaviour.
  • netsuke requires Netsukefile and a Netsuke executable.
  • make requires Makefile and a Make executable.

Custom executable names or paths can be configured with POST_TURN_NETSUKE_BIN and POST_TURN_MAKE_BIN.