Skip to content

Issues workflow fails on every opened issue because issues.cjs is called without its arguments #1786

Open

Description

@joshunrau

The "Issues" workflow fails on every issue that is opened or reopened. The workflow calls require('./.github/scripts/issues.cjs')() with no arguments. The module's default export forwards its args parameter to addPriorityAndDifficulty({ context, github }), so the destructure throws TypeError: Cannot destructure property 'context' of 'undefined' before any API call. All 195 runs GitHub still retains failed, from 2025-09-16 to today. The call has had no arguments since the script was moved out of the workflow in Feb 2024. Every new issue therefore adds a red run to the Actions tab and sends a failure notification. A plain fix would also do the wrong thing. The issue templates no longer contain the Priority and Estimated Difficulty sections the script parses, so it would call addLabels with an empty list. .agents/skills/opening-issues/SKILL.md says titles carry no [Bug]:-style prefix, yet the script would add one to every title, and on reopened it would add a second ([Bug]: [Bug]: …).

Where

.github/workflows/issues.yaml:16-20:

- name: Run Script
  uses: actions/github-script@v9
  with:
    script: |
      require('./.github/scripts/issues.cjs')()

.github/scripts/issues.cjs:4 and :51-54:

function addPriorityAndDifficulty({ context, github }) {
// ...
module.exports = (args) => {
  addPriorityAndDifficulty(args);
  addLabelToTitle(args);
};

Reproduce

  1. Open any issue on the repository.
  2. Open the triggered "Issues" run (gh run list --workflow=Issues --limit 1) and read its log.

Actual: ##[error]Unhandled error: TypeError: Cannot destructure property 'context' of 'undefined' as it is undefined. (for example, run 37676175978).
Expected: either the workflow does something useful and succeeds, or it does not exist.

Tests

No unit or Playwright test can run a GitHub workflow. Verify the fix by opening and then reopening a test issue, and confirming that no "Issues" run fails and that the title is unchanged.

Suggested fix

Delete .github/workflows/issues.yaml and .github/scripts/issues.cjs. The templates no longer feed the label step, and the title step contradicts the documented title convention. If automatic labelling is still wanted, reimplement it against the current templates. Pass { context, github } from the workflow, await both API calls, and skip addLabels when there is nothing to add.

Activity

  1. added
    BugType: existing behavior is wrong
    Priority: LowNice to have, cosmetic or speculative
    Difficulty: LowIsolated change, about 2 hours or less
    Area: InfrastructureDeployment, Docker, CI, logging, CLIs, build and test tooling
    Good First IssueWell-scoped, low-risk and self-contained; a good entry point for a new contributor
    on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: InfrastructureDeployment, Docker, CI, logging, CLIs, build and test toolingBugType: existing behavior is wrongDifficulty: LowIsolated change, about 2 hours or lessGood First IssueWell-scoped, low-risk and self-contained; a good entry point for a new contributorPriority: LowNice to have, cosmetic or speculative

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions