diff options
| author | Philipp Krones <hello@philkrones.com> | 2025-07-09 08:29:50 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-09 08:29:50 +0000 |
| commit | 2ed97eb46614fab1ed2d33c7dcf598f19c8a8787 (patch) | |
| tree | 14c74b3c50aebca940cee4f6a9e7ff8da1f6b842 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | d964e55de2c43e2a5eb7ab3889ca73c8d4ce1370 (diff) | |
| parent | 2dbaf1c7be0f10b958cca7a280eaf6c5ef6d33b4 (diff) | |
| download | rust-2ed97eb46614fab1ed2d33c7dcf598f19c8a8787.tar.gz rust-2ed97eb46614fab1ed2d33c7dcf598f19c8a8787.zip | |
Create summary comment for lintcheck runs (#14816)
Previously https://github.com/rust-lang/triagebot/pull/1985 After a lintcheck run a comment will be created in the PR thread with an overview of the changes, example here https://github.com/Alexendoo/rust-clippy/pull/18#issuecomment-2880441316 (plus the normal GHA debugging experience) It will only comment if there are some changes, if there's already an existing comment it will be updated for each run Similar to https://github.com/rust-lang/team/blob/master/.github/workflows/dry-run.yml The PR number is supplied by the lintcheck run, so technically someone could forge it to be annoying and edit the summaries in other threads, but that is pretty low impact and easy to deal with. There is a `pull_requests` field on the event but as @Kobzol [pointed out to me](https://github.com/rust-lang/triagebot/pull/1985#issuecomment-2869157116) it's not populated for PRs from forks r? @flip1995 changelog: none
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions