Describe the bug
copilot plugin install clones the plugin repo and leaves the .git directory intact. This means the installed plugin is a live git repo that can drift if the user works on the plugin source elsewhere (branch switches, stale state, etc).
Affected version
GitHub Copilot CLI 1.0.40
Steps to reproduce the behavior
copilot plugin install some-skill@some-org
- Check
~/.copilot/installed-plugins/some-org/some-skill/.git — it exists
- If you have the plugin's source repo cloned elsewhere and switch branches there, the installed plugin can end up on a different branch than expected
Expected behavior
Installed plugins should be a static snapshot of the files at install time. The .git directory should not be present — plugin state should be isolated from any source repo the user may have checked out elsewhere.
Additional context
- macOS 15, zsh
- The workaround is to manually
rm -rf .git from the installed plugin directory
Describe the bug
copilot plugin installclones the plugin repo and leaves the.gitdirectory intact. This means the installed plugin is a live git repo that can drift if the user works on the plugin source elsewhere (branch switches, stale state, etc).Affected version
GitHub Copilot CLI 1.0.40
Steps to reproduce the behavior
copilot plugin install some-skill@some-org~/.copilot/installed-plugins/some-org/some-skill/.git— it existsExpected behavior
Installed plugins should be a static snapshot of the files at install time. The
.gitdirectory should not be present — plugin state should be isolated from any source repo the user may have checked out elsewhere.Additional context
rm -rf .gitfrom the installed plugin directory