Repository navigation
Make auto-label.yml runnable: pin issue-labeler, add permissions - #21
Merged
Merged
Conversation
- github/issue-labeler has no floating v3 tag (only v3.0-v3.5), so @V3 failed to resolve and the job died during setup. Pin to v3.5. - enable-versioned-regex is a required input; set it to 0. - The repo's default GITHUB_TOKEN is read-only; grant issues: write so the action can add labels. 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.
Follow-up to #20. That PR moved the issue-labeler config to
.github/labeler.yml. This commit was meant to be part of it, but it was pushed after #20 had already merged, so it never reachedmain.Problem
auto-label.ymlhas never worked. Its only run (Apr 2026) failed during job setup, with no steps run. There are 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.Testing
You can't 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. Addinclude-title: 1if titles should count too.🤖 Generated with Claude Code