Skip to content

Label new issues by package from the issue forms #9397

Open

Description

@Jason3S

Every published package now has an issue label, and each package's bugs link lists its open issues (#9309). Nothing applies those labels yet, so new issues arrive unlabelled.

Agreed so far

  • Both issue forms (.github/ISSUE_TEMPLATE/bug-report.yml and feature-request.yml) get one "Package" dropdown listing every published package, plus "Not sure". It replaces the bug report's "Tool or Library" and "Supporting Library" dropdowns, which are out of date.
  • A small workflow runs when an issue is opened or edited, reads the answer from the form's text, and adds the matching label (the package's directory name under packages/).
  • node ./scripts/fix-package-json.mts --dry-run also checks that the dropdown lists every published package, so it can't drift. The package list comes from scripts/lib/packages.mts.
  • Existing issues are not relabelled. That would be a separate triage pass, if wanted.

Still to decide

  • The dropdown's exact wording: the npm names (@cspell/cspell-types) or the label names (cspell-types).
  • Whether several packages can be selected.
  • What "Not sure" does: no label, or a triage label.
  • What happens when someone edits the answer: add the new label only, or also remove the old one.
Agent instructions

Ask the maintainer the four open questions first, one at a time, with options and a recommendation. Then work in a worktree under .claude/worktrees/. Extend scripts/lib/packages.mts and scripts/fix-package-json.mts so --fix writes the dropdown options and --dry-run fails if they're stale. Add the dropdown to both forms, replacing the two old ones in bug-report.yml. Add a workflow on issues (opened, edited) that labels from the answer, with workflow_dispatch, a github.repository_owner == 'streetsidesoftware' guard, and issues: write only. Update docs/build-and-packaging.md ("Adding a package"). Title: chore:. Follow AGENTS.md.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions