fix(git): include tracked *.lock files in snapshots#199
Merged
joshfriend merged 1 commit intomainfrom Mar 18, 2026
Merged
Conversation
joshfriend
changed the title
joshfriend
force-pushed
the
fix-snapshot-lockfile-excludes
branch
from
f3f299d to
7d3231a
Compare
joshfriend
force-pushed
the
fix-snapshot-lockfile-excludes
branch
from
7d3231a to
3e7cb81
Compare
worstell
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates non-bare git snapshot creation and streaming to exclude only .git lockfiles instead of excluding every *.lock path. Tracked lock files such as package-lock.json, yarn.lock, and Gemfile.lock are now preserved in snapshot archives, and a regression test was added to verify tracked lock files are included while .git/index.lock remains excluded.