Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

`plugin install` fails on repos that use Git LFS: the whole repo's LFS content is downloaded, and one missing object aborts the install

Aberta
  • Algo errado?
#4,962 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
55/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
git, github, shell
Domínio
cli, devtools

Direção de pesquisa

Start at the plugin-install path that builds the GitHub clone command, and reproduce the Git LFS checkout failure using the command and repository layout in the issue. Trace how the plugin path and cache directory are handled. Done means unrelated LFS objects do not abort installation, plugin-path LFS content remains available, and the existing installation flow still works.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

triage
Describe the bug

When a marketplace plugin uses a github source with a path inside a larger repo, copilot plugin install
runs git clone --depth 1 --progress --branch <ref> <url> <cache>/marketplaces/<owner>--<repo> with Git LFS
smudge turned on. Every LFS-tracked file in the repo gets downloaded, including files far outside the
plugin's path. If any one of those objects can't be fetched (for example batch response: Not Found
for an object that was pushed late or never pushed), checkout fails and the install is aborted:

Failed to install plugin: Error: Request plugins.install failed with message: Failed to fetch GitHub plugin <owner>/<repo>: Command failed: git clone --depth 1 --progress --branch main https://github.com/<owner>/<repo> ...\marketplaces\<owner>--<repo>
...
Receiving objects: 100% (29260/29260), 223.35 MiB | 9.17 MiB/s, done.
Downloading <unrelated-data-dir>/.../file.tsv (86 KB)
Error downloading object: ... Smudge error: ... batch response: Not Found
error: external filter 'git-lfs filter-process' failed
fatal: ...: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.

The plugin directory itself contains no LFS files and is about 1.2 MB, but the install downloads about
223 MB of pack data plus every LFS object in the repo, and then fails.

Affected version

Observed on Windows; the clone command is unchanged as of GitHub Copilot CLI 1.0.88.

Steps to reproduce the behavior
  1. Register a marketplace plugin with {"source":"github","repo":"<owner>/<repo>","path":"plugins/<name>","ref":"main"}
    where the repo tracks unrelated files with Git LFS (<data-dir>/** filter=lfs).
  2. Make one LFS object under <data-dir> unavailable on the server (or just use a large LFS data set).
  3. Run copilot plugin install <name>@<marketplace>.
  4. The install downloads all LFS content, then fails at checkout with smudge filter lfs failed.
Expected behavior
  • The plugin fetch shouldn't run the LFS smudge for content outside the plugin path. At minimum,
    set GIT_LFS_SKIP_SMUDGE=1 for the clone, then git lfs pull --include "<path>/**" only when the
    plugin path actually contains LFS pointers.
  • A failure to download content outside the plugin path shouldn't fail the install.
  • Ideally, combine this with a partial clone plus sparse checkout of path (#2399), so only the plugin's files are downloaded.
Additional context
  • Workaround: set GIT_LFS_SKIP_SMUDGE=1 before copilot plugin install, and delete the half-cloned
    marketplaces/<owner>--<repo> directory first.
  • Related: the cache directory is keyed only by <owner>--<repo>. Two plugins from the same repo on
    different refs look like they share one checkout, so the cache key should probably include the ref.
  • OS: Windows 11 (also affects macOS/Linux, because the clone behavior is the same)
Linguagem predominante
Shell
Estrelas
11.2k
Forks
1.9k
Merge médio
17h 6min
PRs com merge (30d)
5

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/copilot-cli

Todas as issues de github/copilot-cli

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.