Repository navigation
Conversation
The Issues workflow calls issues.cjs with no arguments, so every opened or reopened issue fails while destructuring context and github. Delete the workflow and script instead of passing those arguments: the label step adds Difficulty labels that contradict triage, and the title prefix contradicts the documented title convention. Co-Authored-By: Grok 4.7 Co-authored-by: David <dyk1454683243-sudo@users.noreply.github.com>
joshunrau
approved these changes
Nov 5, 2026
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.
Fixes #1786
The Issues workflow fails on every issue that is opened or reopened.
.github/workflows/issues.yamlcallsrequire('./.github/scripts/issues.cjs')()with no arguments, and the script immediately destructures{ context, github }. That throwsTypeError: Cannot destructure property 'context' of 'undefined'before any API call, which is why every retained run of the workflow is red.Passing
{ context, github }would turn the run green and then do the wrong thing. The script reads Priority and Estimated Difficulty out of the issue body and adds those labels, and it prefixes the title with[Kind]:(again on each reopen). The maintainer recommendation on #1786 is to delete both files and not reimplement the label or title step: triage replaces the reporter's Difficulty estimate most of the time, so an add-only step leaves two Difficulty labels, and the title prefix contradicts the documented title convention.This deletes
.github/workflows/issues.yamland.github/scripts/issues.cjsonly.knip.tsstill ignoresgithub-scriptbecause.github/scripts/release.cjstypes its arguments withimport('github-script'). That entry stays. Open PR #1822 drops that JSDoc fromrelease.cjs; whichever change lands second should remove the unusedgithub-scriptignore (and its comment) sopnpm knipstays clean.Verified by confirming both files are gone, that nothing else references
issues.cjsor the Issues workflow, and thatrelease.cjsstill referencesgithub-script. No unit or Playwright test runs a GitHub workflow, and.github/scriptsis outside the coverage include.