Comment test #18
Closed
Comment test #18
Conversation
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
Alexendoo
force-pushed
the
lintcheck-comment
branch
3 times, most recently
from
b73f7f5 to
08faa4d
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
08faa4d to
218d532
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
218d532 to
7431de1
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
7431de1 to
98322d5
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
98322d5 to
e0012d8
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
e0012d8 to
27778f6
Compare
|
Lintcheck changes for 6d5b9c2
This comment will be updated if you push new changes |
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
27778f6 to
1fe26b2
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
1fe26b2 to
3101883
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
3101883 to
df5b773
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
dde8110 to
82a743a
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
82a743a to
6947f85
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
6947f85 to
0fa99c8
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
0fa99c8 to
05be98d
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
05be98d to
6973edb
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
6973edb to
863b72e
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
863b72e to
f9c7caa
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
f9c7caa to
40b768f
Compare
Alexendoo
force-pushed
the
lintcheck-comment
branch
from
40b768f to
6d5b9c2
Compare
github-merge-queue bot
pushed a commit
to rust-lang/rust-clippy
that referenced
this pull request
Jul 9, 2025
Previously rust-lang/triagebot#1985 After a lintcheck run a comment will be created in the PR thread with an overview of the changes, example here Alexendoo#18 (comment) (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](rust-lang/triagebot#1985 (comment)) it's not populated for PRs from forks r? @flip1995 changelog: none
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.
changelog: none