Skip to content

Files to copy does not match nested .env files #320

Description

@adamatan

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions