{"version":"2.1.274","anchor":"marketplace-git-clone-path-refactored-lfs-warning-now-surfa","canonical_anchor":"git-lfs-pointer-file-detection-with-a-new-warning-message","heading":"Git LFS files in marketplace checkouts now get pointer-file warnings, and --skip-lfs is a documented no-op","tier":"notice","area":"Plugin Marketplace","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/marketplace-git-clone-path-refactored-lfs-warning-now-surfa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Git LFS files in marketplace checkouts now get pointer-file warnings, and --skip-lfs is a documented no-op\n\nClaude Code warns when marketplace files tracked by Git LFS were checked out as pointer stubs instead of real content\n\n**What**\n\n- New code scans a working tree's git index (and any nested `.gitattributes` files) for files tracked with `filter=lfs` (Git Large File Storage), checks whether they were checked out as literal LFS pointer files rather than real content, and surfaces a warning telling the user to run `git lfs pull` if so.\n\n- Marketplace add\/refresh logic was restructured around a shared clone helper, whose result now feeds a new step that logs and reports this git-LFS warning after the clone completes, replacing the old approach of passing a `skipLfs` option inline to the clone call.\n\n- The `--skip-lfs` marketplace option's description was rewritten to clarify it now has no effect: Claude Code's own git never downloads LFS content regardless of the setting, LFS-tracked files are always checked out as pointers, and getting the real content requires running `git lfs pull` manually in the marketplace checkout.\n\n**Why**\n\nThis makes it clear to users when marketplace plugin files are just LFS pointer stubs rather than real content, and clarifies that `--skip-lfs` doesn't need to be set since LFS content is never fetched automatically anyway.\n\n- Area: Plugin Marketplace\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}