Repository navigation
Fix issue labeling: move labeler config out of workflows/, make auto-label.yml runnable - #20
Merged
Merged
Conversation
.github/workflows/labeler.yml was never a workflow: it is the label -> regex
config for github/issue-labeler. Because it sat in .github/workflows, GitHub
tried to parse it as a workflow on every push and rejected it ("workflow file
issue"). Meanwhile auto-label.yml looks for its config at .github/labeler.yml,
which did not exist.
Moving the file to .github/labeler.yml stops the bogus failing run and gives
auto-label.yml the config it expects.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
1.
labeler.ymlfailing on every push.github/workflows/labeler.ymlis not a workflow. It is the label → regex config forgithub/issue-labeler. It was committed into.github/workflows/(ce3972e). GitHub treats every file in that folder as a workflow, so on every push it tried to parse it, found noon:/jobs:, and rejected it ("This run likely failed because of a workflow file issue", 0s).auto-label.ymlreads its config from.github/labeler.yml, which didn't exist. The two files weren't duplicates. One was the other's config, saved in the wrong folder.Fix:
git mv .github/workflows/labeler.yml .github/labeler.yml, with the content unchanged.2.
auto-label.ymlcould never have workedIts only run (Apr 2026,
issues: opened) failed during job setup with no steps run. Three problems:github/issue-labeler@v3doesn't resolve: upstream has onlyv3.0–v3.5tags, with no floatingv3@v3.5(latest, Aug 2026)enable-versioned-regexis a required input and wasn't setenable-versioned-regex: 0GITHUB_TOKENpermission is read, so adding labels would 403permissions: contents: read, issues: writeThe trigger (
issues: opened) is unchanged and fits what the workflow does.Testing
You can't fully test this from a PR, because
issuesworkflows run only from the default branch. After merging, open a test issue whose body contains e.g. "crash" and check that it gets thebuglabel. By default the action matches only the issue body (include-title: 0). Addinclude-title: 1if titles should count too.🤖 Generated with Claude Code