Problem
A project with *.env* in “Files to copy” does not copy evals/.env into a new task worktree.
Details
copy_matching only searches the directory named in the pattern, so a pattern without a path searches the repo root. Its matcher also rejects patterns with more than one *, meaning *.env* matches nothing, even at the root.
For now, .env* and evals/.env* can be listed separately.
Acceptance
- Support multiple wildcards and a recursive pattern such as
**/.env*.
- Copy matching files into the same relative paths in the worktree.
- Add
**/.env* as an example in the help text above the “Files to copy” box, explaining that it matches files at any depth.
- Test root and nested
.env files while preserving exact-path and directory-copy behavior.
Problem
A project with
*.env*in “Files to copy” does not copyevals/.envinto a new task worktree.Details
copy_matchingonly searches the directory named in the pattern, so a pattern without a path searches the repo root. Its matcher also rejects patterns with more than one*, meaning*.env*matches nothing, even at the root.For now,
.env*andevals/.env*can be listed separately.Acceptance
**/.env*.**/.env*as an example in the help text above the “Files to copy” box, explaining that it matches files at any depth..envfiles while preserving exact-path and directory-copy behavior.