Repository navigation
test(e2e-command): use the released comment-triggered-check/v1 - #79
Merged
Merged
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
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
The command callers here pointed at the action branch
devops-1843/test-e2e-run-replywhile loft-sh/github-actions#360 was tested end to end (#76). That PR is merged, andcomment-triggered-check/v1now points at its merge commit, which is the same code.What this PR changes
Every caller uses
comment-triggered-check/v1again. The reply stays on, so this repo keeps exercising it. The action branch can then be deleted.How it was tested
The only change is the action ref, and actionlint is clean. The next command on a test PR runs on
v1.Related to DEVOPS-1843