CI: fix missing slash command input args #37564
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
aaronsteers
commented
Apr 25, 2024
aaronsteers
commented
Apr 25, 2024
aaronsteers
commented
Apr 25, 2024
aaronsteers
commented
Apr 25, 2024
|
Merging to resolve breakage from last PR. This should be a no-op, except to make sure other slash commands don't fail. |
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
Resolves an issue where an unused "pr" arg sent to a slash command would cause the workflow to fail.
How
Defines "pr" args and marks them unused and optional, when not used.
Review guide
User Impact
Can this PR be safely reverted and rolled back?