Repository navigation
Fix support window issue-bot Invalid inputs failure - #727
Merged
Merged
Conversation
imjohnbo/issue-bot@3188c6c (v3.4.5) is already the latest release, so the workflow's every-3-months run was not failing due to an outdated action version. It fails because that version's checkInputs() requires a non-empty labels input whenever close-previous is true, and this workflow never set labels, causing "Error: Invalid inputs" on every run. Adding a labels value satisfies that requirement and lets close-previous correctly find and close the prior issue.
1 task
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
1 participant
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.
Summary
Support Windows Issue Createrworkflow has been failing every quarterly run withError: Invalid inputs.imjohnbo/issue-bot@3188c6cis already pinned to the latest release (v3.4.5) — this is not a stale-version issue.labelsinput wheneverclose-previous: trueis set, and the workflow never setlabels, so the action always threw before doing anything.labels: "support-window"so the required-inputs check passes andclose-previouscan correctly find/close the prior issue by label.Test plan
.github/workflows/support-window-issue-creator.yml(or a manual re-run) creates the issue without anInvalid inputserrorsupport-windowlabel yet); subsequent runs will close-previous correctly