Conversation
|
CC @dybucc |
|
I guess it works based on the fact it has a similar diff to the one I submitted |
|
I'm not at the computer right now, but we might need to adjust the CI workflow, because it didn't fire. |
|
You mean automatically? I don't think it's meant to run outside the scheduled |
|
No, I mean the usual CI workflow: https://github.com/rust-lang/rust-analyzer/blob/master/.github/workflows/ci.yaml. We check for |
|
I guess we should explicitly designate token as sth other than default |
|
Would that help? The workflow filed the PR, so I don't think it's a permissions issue. |
|
Yeah, AFAIK everything triggered with |
|
To elaborate more,
|
bf50983 to
ddae703
Compare
|
We've lost our Clippy lints. |
|
Not really sure what you mean, beyond the fact that the |
|
The URL at rust-analyzer/xtask/src/codegen/lints.rs Line 86 in ddae703 hover_clippy_lint) to fail, because it no longer finds the lint. I didn't check your branch, but the diff here has:
|
|
Then I guess this PR is unrelated to this issue. Still, it seems like the |
| cmd!( | ||
| sh, | ||
| "curl https://rust-lang.github.io/rust-clippy/stable/lints.json --output {lints_json}" | ||
| "curl -f https://raw.githubusercontent.com/rust-lang/rust-clippy/21fd71e3fe6eb063cfb619ecc37b1023f5283894/beta/lints.json --output {lints_json}" |
There was a problem hiding this comment.
Changed this to take the last working version.
Weekly lint updates for
crates/ide-db/src/generated/lints.rs.Closes #21947