Skip to content

Validate the comment triggered suite (do not merge) - #45

Closed
ivan-pinatti wants to merge 1 commit into
mainfrom
chore/validate-comment-gate
Closed

ivan-pinatti wants to merge 1 commit into
mainfrom
chore/validate-comment-gate

Conversation

@ivan-pinatti

Copy link
Copy Markdown
Collaborator

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-tests comment here should demonstrate:

  • the gate job authorizes the commenter against the list on main, and reacts to the comment only once it has
  • the head SHA is resolved from the API, and Tests Verified is published as pending against it
  • the suite job checks out the merge ref and proves its second parent is that same head before spending anything
  • is_fork reads false, so the Docker Hub credentials are passed and the run is treated as trusted
  • the publish job writes the terminal status against the head SHA, whatever the suite did

The 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.

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.
@ivan-pinatti

Copy link
Copy Markdown
Collaborator Author

/run-tests

@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ad5925c7-c4ac-4d7d-9c5d-49f9a0c54fea

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

✅MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ EDITORCONFIG editorconfig-checker 1 0 0 0.26s
✅ REPOSITORY betterleaks yes no no 0.61s
✅ REPOSITORY checkov yes no no 12.02s
✅ REPOSITORY trivy yes no no 7.51s
✅ SPELL cspell 2 0 0 2.35s

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@ivan-pinatti

Copy link
Copy Markdown
Collaborator Author

/run-tests

@ivan-pinatti

Copy link
Copy Markdown
Collaborator Author

/run-tests

@ivan-pinatti

Copy link
Copy Markdown
Collaborator Author

/run-tests

@ivan-pinatti

Copy link
Copy Markdown
Collaborator Author

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.

@ivan-pinatti
ivan-pinatti deleted the chore/validate-comment-gate branch August 15, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant