@gw-config-management

Configuring worktree workflows for a monorepo requires setting core fields like root, defaultBranch, and autoCopyFiles. You can use provided templates to standardize team setups and ensure consistent environment handling across the project.

To auto-copy environment files into new worktrees, you define autoCopyFiles patterns in your configuration. This ensures required secrets and environment files are available in new worktrees with safe defaults and team-wide templates.

Yes, you can use gw-tools configuration templates for Next.js, Node.js APIs, and React SPAs. The configuration process provides ready-made examples to tailor worktree workflows and align per-repo configurations for these specific frameworks.

Initializing gw-tools for a new project involves applying core configuration fields such as root, defaultBranch, and updateStrategy. You can use the quick start guidance to set up auto-copy patterns and start creating worktrees with consistent configuration.

Secrets not copying to new git worktrees usually indicates missing or incorrect autoCopyFiles patterns in your configuration. Troubleshooting configuration issues requires verifying these patterns to ensure environment files are available with safe defaults.