Repository navigation
test(e2e-command): reply to each command with its runs - #76
Merged
Merged
Conversation
This was referenced Nov 6, 2026
Merged
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
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.
What happened
loft-sh/github-actions#360 adds an opt-in reply to
comment-triggered-check. Comment-triggered workflows only run from the default branch, so the reply can only be tried end to end frommainhere.What this PR changes
Both command callers turn the reply on.
/test-e2e(pro + oss) and/test-platform-e2esetreply,comment-idand a row label. After each dispatch they calllinkwith the run URL thatgh workflow runprints./test-platform-e2edispatches one job per--runsentry, like loft-enterprise. Parallel jobs then link the same reply, which is the case the review on #360 raised.The suite stand-ins can redraw the reply. Their finish jobs get
pull-requests: write.The shared "started" comment is gone from the
/test-e2ecaller, because the reply replaces it.Every caller points at the action branch
devops-1843/test-e2e-run-reply. They move back tocomment-triggered-check/v1once #360 merges and the tag advances.How it was tested
actionlint is clean for the changed workflows. The end-to-end run happens on a test PR after this merges.
Related to DEVOPS-1843