git-worktree-precommit-hook-flutter-failure

Flutter analyze fails in git worktrees because git sets the GIT_DIR environment variable to a worktree-style path during hook execution, which breaks dependency resolution during pub get. Unsetting GIT_DIR, GIT_INDEX_FILE, and GIT_WORK_TREE before flutter commands fixes this.

To fix pre-commit hook failures, unset the GIT_DIR, GIT_INDEX_FILE, and GIT_WORK_TREE environment variables in your hook script after completing required git operations but before executing any flutter or dart commands to ensure reliable dependency resolution.

Yes, you need to unset GIT_WORK_TREE, along with GIT_DIR and GIT_INDEX_FILE, before running dart commands in pre-commit hooks. This prevents git environment variables from interfering with Flutter tooling and dependency resolution in worktree workflows.

Running flutter pub get inside a pre-commit hook fails with git worktrees because git injects environment variables that disrupt the process. You must unset GIT_DIR, GIT_INDEX_FILE, and GIT_WORK_TREE before invoking flutter commands for pub get to succeed.

The best way to stabilize Flutter pre-commit hooks across multiple worktrees is introducing a targeted unset step for GIT_DIR, GIT_INDEX_FILE, and GIT_WORK_TREE. This ensures a consistent environment for Flutter tooling during commits in parallel feature workflows.

Manual flutter analyze passes because your shell environment is clean, but pre-commit hooks fail because git automatically sets GIT_DIR and related variables during execution. Unsetting these variables before flutter commands ensures the hook matches manual behavior.