Repository navigation
Validate the comment triggered suite (do not merge) - #45
ivan-pinatti wants to merge 1 commit into
Conversation
Not for merging. The suite has to be asked for on a pull request that counts as a code change, or the docs only waiver answers first and nothing is exercised.
|
/run-tests |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts
|
|
/run-tests |
|
/run-tests |
|
/run-tests |
|
Closing: this did its job. It caught the concurrency bug on the first real /run-tests, then proved the gate, the merge-parent check, the non-fork credential path and the status lifecycle end to end, and finally carried the first fully green suite since the runner image bump. The probe file was never meant to merge. |

Do not merge
A throwaway pull request that exists to exercise the comment triggered suite now that #42 is on
main, then to be closed.What a
/run-testscomment here should demonstrate:gatejob authorizes the commenter against the list onmain, and reacts to the comment only once it hasTests Verifiedis published aspendingagainst itsuitejob checks out the merge ref and proves its second parent is that same head before spending anythingis_forkreads false, so the Docker Hub credentials are passed and the run is treated as trustedpublishjob writes the terminal status against the head SHA, whatever the suite didThe suite itself is expected to fail in
Start stack, which is the podman hang tracked in #44 and has nothing to do with the gate. A failing suite still validates the machinery here: the point is that the status lands, on the right commit, from the right job.