**/*.lock linguist-generated=false #843
Merged
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.
https://docs.github.com/en/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github
default to showing lock file diffs in pr view. they are defaulted to not showing since people often like to ignore their noise. with granular changes i think it's worth looking over them to make sure there aren't unexpected changes. in the case of merging large branches with too many lock changes to review, go ahead and mark it viewed and github will keep it hidden until it is changed.
like Chia-Network/chia-blockchain#18939