Skip to content
Latchkey

actions/labeler "Error: not found label"

labeler applies labels named in its config. If a referenced label has not been created in the repo, the apply call fails with "not found label".

What this error means

The labeler step fails with "Error: not found label" naming a label from labeler.yml.

github-actions
Error: not found label : "needs-review"
##[error]Error: not found label : "needs-review"

Common causes

Label missing in the repo

The config names a label that was never created under Issues > Labels.

Label name mismatch

A typo or case difference makes the configured name not match any existing label.

How to fix it

Create the label or fix the config name

  1. Create the missing label in the repo, or correct the name in .github/labeler.yml.
  2. Grant pull-requests: write so labeler can apply labels.
  3. Re-run the workflow.
.github/workflows/labeler.yml
permissions:
  contents: read
  pull-requests: write
steps:
  - uses: actions/labeler@v5

How to prevent it

  • Manage labels with an action (or seed them) so config and repo stay in sync.
  • Keep label names in labeler.yml identical (case included) to the repo labels.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →