Repository navigation
Conversation
GitHub made issue types and fields GA for personal accounts on 2026-11-11. Declare the set in config/infra.json: the three default types plus Watch for robot-filed trackers, and Priority plus an Upstream link field. labels:sync writes them to the account, and infra:check reads /repos/:slug/issue-types and scans gh --type flags.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
aadhar-sh | 0ebb1b5 | Commit Preview URL Branch Preview URL |
Nov 12 2026, 03:10 AM |
The API lists options by name, so the first sync planned a reorder it had just written.
Contributor
Wire-size diff vs merge base
Brotli q11, the quality the edge serves. Every number here is deterministic: Client assetsNo change. 40 files, 245.02 KiB Brotli total. PagesNo change. 77 files, 720.36 KiB Brotli total. Worker bundleNo change. 299.54 KiB gzip. Dictionary transportFamily dictionary acquisition: no change, 14.50 KiB q11.
Head tags vs merge baseNo change. 77 documents, every title, description, canonical, robots, |
This branch has not been deployed
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.
GitHub made issue types and fields GA for personal accounts today (changelog). The account already carries the 3 default types, none of the 19 issues here has one, and fields aren't turned on.
This declares both in
config/infra.jsonbeside the labels, the same way:Task,Bug,Feature, plusWatchfor robot-filed trackers (17 of the 19 issues), and the fieldsPriorityplusUpstream, a text field holding the link a watch waits on.labels:syncwrites them through/user/issue-typesand/user/issue-fields.infra:checkvalidates the declaration offline, scans workflows forgh issue create --typenames it doesn't declare, and diffs/repos/:slug/issue-typeslive. test-order and node-support-window now file asWatch, and the Workers triage routine files asBug.Verification: before the sync,
infra:checkwith a repo token failed on the missingWatch. Afterlabels:sync -- --confirmcreated Watch, Priority and Upstream, it passes, and a second sync plans 0 changes. Planting--type Wtchin test-order.yml fails the scan by name. The contract suite passes (1760 pass, 18 skip).The account is already synced. Turning fields on created no defaults (
/user/issue-fieldswas empty), so nothing needed pruning. Before merging, paste the routine prompt into the routine again, since it changed.Limits: the API lists field options by name, so the sync sorts them by
prioritybefore comparing.infra:checkdoesn't check fields live (they have no repo-scoped REST read), and pinning a field to a type has no REST endpoint at all. timbrado's canary issues stay untyped until timbrado learns--type. Happy to drop the field half from this PR if you'd rather land types alone.All 19 existing issues now carry a type: 17 Watch, 1026 as Task, 338 as Feature.