chore: stop tracking generated lcov.info#58
Merged
Merged
Conversation
lcov.info is a coverage artifact regenerated by npm test and is already listed in .gitignore, but it remained tracked from before that entry was added. Untrack it so it stops appearing in diffs. Co-Authored-By: Claude Opus 4.8 <[email protected]>
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
1 participant
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.
lcov.infois a coverage report regenerated bynpm teston every run, and it's already listed in.gitignore. But it was committed before that.gitignoreentry existed, so git kept tracking it —.gitignorehas no effect on already-tracked files. As a result it shows up in unrelated diffs whenever tests run.This untracks it via
git rm --cached(local file kept), so it stays ignored going forward. No code or CI consumes the committed copy.🤖 Generated with Claude Code