Repository navigation
Migrate issue type labels to proper issue types #1383
Description
Activity
State of things: the organisation has the three types Task, Bug and Feature, all enabled; none of the 531 issues carries one; no workflow in
.github/workflowsreads a label, so the templates and the existing issues are the whole of it.Templates and the contributing guide — #1384:
bug_report.mdsetstype: Bug,suggest_idea.mdsetstype: Featureinstead of attachingProposal,ask_question.mdkeeps theQuestionlabel and no type (a question is not a work item).CONTRIBUTING.md's Types of issues now separates the two: the type is the kind of thing an issue is, the labels its state (Accepted,Not now,Opinions wanted,up-for-grabs) and its area.The existing issues — the mapping I would apply, from a dry run over all 531:
labels type issues Bug,Minor bugBug 134 Proposal,Design documentFeature 210 Agentic goalTask 4 anything else ( Question,Opinions wantedalone, unlabelled)untyped the rest Four issues carry both a bug label and
Proposal(#371, #541, #545, #548) and go to Bug.Minor bugfolds into Bug — a type has no severity — so if the distinction is worth keeping it becomes a label such asMinorrather than a type; say if you want that.Design documentandAgentic goalstay as labels beside the type, since they say more than it does.Two things I have not done and will on your word: the bulk write itself (a script that sets the type on those 348 issues, and with a second flag removes
Bug,Minor bugandProposalfrom the ones that got their type from them — removing is the destructive half, so it is separate), and anything at the organisation level, which is yours: whether Task stays the default for a new issue. My recommendation: keep Task as a type — the docket (#1019), the goals and migrations like this one are neither bugs nor features — but not as the default, so that an issue a template did not type shows up untyped and gets triaged, rather than counted as work by omission.Questions and opinions wanted are really Discussions, not Issues. These should be redirected. Existing answered ones can be closed if no work item arises from it.
Agentic goal is really its own type, the task type might want to be renamed to Goal - it's like a meta-issue (Epics?) that spawn work items.
Default should probably be Goal because it's the easiest to write for - bugs or features can be agent triaged. In fact it may even be better to accept anything and let you determine what to do (but the bar to reject doing anything would be quite high - we do all maths!), so that the bar of participation is minimal.
You are authorized to do this restructuring of issues now.
Also, if you don't read and comment to Discussions items already, add that to your workflow.
- added a commit that references this issue
on Sep 16, 2026 Done in the repository, on #1384 (second commit):
- Goal is the type and the default: a goal template is first in the chooser with the bar as low as it goes ("say what you want to be true — you do not have to know whether it is a bug or a feature; it is mathematics, and we do all of it"),
bug_reportandsuggest_ideaset Bug and Feature, the question template is gone, and the chooser's contact links send questions to the Q&A category and ideas-to-talk-over to Ideas.CONTRIBUTING.mdsays Goal / Bug / Feature, and that questions and opinions are Discussions, redirected and closed once answered unless a work item came of it. - Discussions are in the sweep:
AGENTS.md's working practice now reads them beside the two comment endpoints every round, with the GraphQL query. (There are four; the two Q&A ones are marked answered.) - The migration is
.github/additional/migrate-issue-types.sh, dry by default: it renames the organisation'sTasktype toGoal, types every issue (Bug 134, Feature 210, Goal 162 — theAgentic goalfour plus every untyped non-question), takesBug/Minor bug/Proposaloff with--remove-labels, and with--close-questionsredirects and closes the three openOpinions wanted-only issues (Let's steal some issues from https://github.com/davidedc/Algebrite! >:3 #180, Roots vs fractioned powers? #204, Syntax for Piecewise? #326; the closedQuestionones stay closed).
Two things stop me from running the write half myself right now: the type rename is an organisation-level call (
PATCH orgs/asc-community/issue-types/…, org admin), and my session's permission gate refuses bulk writes to the tracker.bash .github/additional/migrate-issue-types.sh --apply --remove-labels --close-questionsfrom an admin'sghdoes the whole thing in one go, after #1384 merges; or grant it and I run it.- Goal is the type and the default: a goal template is first in the chooser with the bar as low as it goes ("say what you want to be true — you do not have to know whether it is a bug or a feature; it is mathematics, and we do all of it"),
- added 4 commits that reference this issue
on Sep 16, 2026 - added 2 commits that reference this issue
on Sep 22, 2026 - added a commit that references this issue
on Sep 22, 2026 - added a commit that references this issue
on Sep 22, 2026 Is this resolved by #1384?
#1384 did the repository side and was
Part ofthis. The template asks for no kind and leaves the type to triage,CONTRIBUTING.mdandAGENTS.mddescribe the four types, the organisation'sTaskbecameMaintenanceandGoalwas added, and the one-time migration removed the type labels.What's left is triage. Seven open issues had no type. My three now have one (#898, #1498, #1508). The other four are WhiteBlackGoose's: #204, #286, #326 and #534. Once those are typed, this can close.
See if those are now typed correctly
Closing as done. #1384 moved the templates and docs to issue types, and as of today all 93 open issues have a type and every non-Goal has a milestone.
Update all workflows and templates to use native issue types instead of labels. Also need to consider if we want the default "task" issue type to mean something or if it should be removed.