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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run a diff of lintcheck against the merge base for pull requests #10398
Run a diff of lintcheck against the merge base for pull requests #10398
Changes from all commits
477b0c6
feb0671
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using cache here is a bit weird IMO. I think the
upload-artifacts
action would fit better here? Or am I missing something? https://github.com/actions/upload-artifactThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does do some caching as well as act as a way to share it between steps e.g. here
base
had a cache hitI don't know if you can do that with artifacts, mostly I went with cache because I'm already familiar with it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok. True,
base
can have cache hits between PRs based on the same master commit.head
however will never have a cache hit, neither willdiff
. I think the cleaner way would be to just cachebase
. To share thejson
files however, it would be cleaner to use{down,up}load-artifacts
IMO.But this is a NIT on the action
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It feels like lintcheck is becoming more and more a monster that can do everything related to lint checking. I think this makes sense, especially if we might consider extracting lintcheck to be used outside of Clippy as well. We should consider merging
lintcheck/src/popular-crates.rs
into this as well.This is a followup though, nothing that should be done in this PR