Repository navigation
CI: classify issues by type and package from plain words - #297
Merged
Merged
Conversation
Issues opened with gh issue create or by hand had no dropdown and got no labels. Add bug, documentation, enhancement (title words), python, github_actions, and jvm/native from plain words. Only existing labels, only added. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Same selection as assign-milestone.yml; never replaces an existing milestone; a dry run logs it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 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.
Issues opened with
gh issue createor by hand get no labels and no milestone fromclassify-issue.yml: it only reads the bug form'sPackagedropdown and four topic words, so #295 and #270 stayed bare, and Roberto and I label by hand.This extends the same keyword table, no model call, only labels that already exist, only added, never removed. One issue may get several labels:
bug,documentation,enhancement: words in the title only (a body mentions "error" or "example" too often to say what the issue is).python:python,wheel,pip,uv add,import arcadedb,pytest,JPypein the title or body.github_actions:CI,workflow,GitHub Actions,runnerin the title or body.jvm,native: when the dropdown is absent, a title that names a package decides alone; otherwisearcadedb-jvm,JPype,JVM build,native buildin the body.dependenciesis left to Dependabot.assign-milestone.ymlselects it; no open milestone sets nothing, an existing milestone is never replaced. Theworkflow_dispatchdry run logs the milestone it would set.Bot-opened issues are still skipped, and the dry run path is unchanged. The header comment documents each group.
pre-commit(includingactionlint) passes on the file.Proof without touching any issue: I dispatched the workflow in dry-run mode on this branch (head
7bfc82e) and copied the lines from the run logs.bug,github_actions,native,python26.12.1github_actions,python26.12.1native,python,vector26.12.1enhancement,jvm,native,python26.12.1concurrency,documentation,jvm,performance,python,vector26.12.1github_actions,jvm,performance,python26.11.1documentation,jvm26.12.1native,python,vector26.12.1Body words are a guess, so a wrong label is fixed by hand like any label (#255 shows it: the body-wide words add
jvmandperformance). Theopenedpath itself can only be seen on the next new issue.🤖 Generated with Claude Code