fix: keep lockfiles visible to Greptile#185
Merged
Merged
Conversation
Greptile SummaryKeeps dependency and provider lockfiles visible to Greptile by removing their patterns from the generated-file ignore configuration. Confidence Score: 5/5The PR appears safe to merge because the configuration change precisely makes lockfiles reviewable without altering the remaining exclusions. The updated configuration remains valid JSON and removes only the lockfile ignore entries described by the PR.
|
| Filename | Overview |
|---|---|
| .greptile/config.json | Removes five lockfile patterns from ignorePatterns while preserving the remaining generated-file exclusions and valid JSON structure. |
Reviews (1): Last reviewed commit: "fix: keep lockfiles visible to Greptile" | Re-trigger Greptile
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
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.
Remove lockfiles from Greptile ignore patterns so dependency and provider resolution changes remain reviewable.
Follow-up to the generated-file configuration PR.