dist/tools/check_pr: also error on Github commits#22358
Conversation
|
Ah, overlooked |
AnnsAnns
left a comment
There was a problem hiding this comment.
This sounds solid but as far as I understand your test should not work since it checks out master for the commit-msg CI workflow and not the PR itself 😄
crasbe
left a comment
There was a problem hiding this comment.
This is handeled by https://github.com/RIOT-OS/RIOT/tree/master/dist/tools/pr_check
I think there is still some value to making the commit-msg error clearer though |
f191401 to
7a16b12
Compare
In the sense that https://github.com/RIOT-OS/RIOT/actions/runs/27146516631/job/80125660302?pr=22358 would also show a message about it being a fixup. I'd argue that it might actually make more sense to make commit-msg wait for pr_check though so that it doesn't throw like 3 CI errors for a single issue |
|
I've changed the proposal now to what I initially wanted to cover: Erroring out on automatic "Github code review application" commits. |
|
Can you test that in this PR real quick? Add a bogus commit with "Apply suggestions from code review"? |
Co-authored-by: mguetschow <mikolai.guetschow@tu-dresden.de>
|
Actually I just noted that Github would suggest "Apply suggestion from " for single apply instead of batch-apply. See the last commit to catch both. |
Co-authored-by: mguetschow <mikolai.guetschow@tu-dresden.de>

Contribution description
Right now, fixup commits usually just error out because they go over the commit message length limit.Automatic Github commits ("Apply suggestions from code review") just fail because they are missing the colon. Now we show the typical "squash needed" message instead.Testing procedure
CI should fail on this PR until I remove the fixup commit.Declaration of AI-Tools / LLMs usage:
AI-Tools / LLMs that were used are: