Feature summary
Allow configuring the location where GitHub Copilot app creates worktrees via repository settings
What problem are you trying to solve?
Currently, the GitHub Copilot app creates worktrees in a centralized/global location on disk.
This approach introduces a few challenges:
-
Worktrees are not colocated with the repository, making navigation harder
-
Developer workflows that expect worktrees inside or near the repo (e.g., monorepos, tooling, scripts) break or require additional setup
-
Disk organization becomes fragmented across projects
-
It is difficult to apply repo-specific conventions for worktree layout
-
Teams cannot standardize the worktree structure across environments
Proposed solution
Introduce a configurable setting either is settings of a repo in GitHub Copilot App or in .github/github-app.yml to control worktree location
Workflow impact
No response
Installation context
No response
Additional context
No response
Feature summary
Allow configuring the location where GitHub Copilot app creates worktrees via repository settings
What problem are you trying to solve?
Currently, the GitHub Copilot app creates worktrees in a centralized/global location on disk.
This approach introduces a few challenges:
Worktrees are not colocated with the repository, making navigation harder
Developer workflows that expect worktrees inside or near the repo (e.g., monorepos, tooling, scripts) break or require additional setup
Disk organization becomes fragmented across projects
It is difficult to apply repo-specific conventions for worktree layout
Teams cannot standardize the worktree structure across environments
Proposed solution
Introduce a configurable setting either is settings of a repo in GitHub Copilot App or in .github/github-app.yml to control worktree location
Workflow impact
No response
Installation context
No response
Additional context
No response