Repository navigation
GitHub: create a GitHub-backed list from a repository #73
Description
Product behaviour (/help/lists)
The new-list flow has two tabs: Local List and GitHub-backed List. On the GitHub tab:
- pick a repository you have access to;
- enter a list title (defaults to the repo name);
- optionally set a parent list;
- toggle Public list.
GitHub-backed lists show a GitHub icon and sync issues from the repo. Rows map to issues — add a row creates an issue, edit updates it, delete closes it.
Prerequisite: GitHub connected with the Issues scope. An account linked for sign-in only needs "Reconnect for GitHub Issues".
Acceptance criteria
- A GitHub-backed tab in the new-list flow with a repo picker (grouped by org, paginated).
- Title defaults to the repo name; parent list and public toggle available.
-
ListSummary.source/githubRepo/githubRepoPrivateare modelled and a GitHub icon marks such lists. - Missing Issues scope is detected up front and offers the reconnect handoff rather than failing at create.
Activity
Adron commentedon Sep 16, 2026
Live probe results from the service layer (#72 / PR #142)
GET /api/user/identitiesshows providergithub, usernameInterlinedListMessenger. The200 []from/reposand/orgsmeans that GitHub account owns no repos and joins no orgs — not that nothing is linked. So:/api/user/identities(GetGitHubLinkStateAsync→GitHubLinkState), never from an empty collection. Inferring "not linked" from[]would show a Connect prompt to an already-connected user.ClassifyGitHubFailure/GitHubFailureReasonexist as a backstop, withNotLinkedflagged unverified.All nine endpoints, live
GET /reposGET /repos?org=githubGET /repos?org=dotnetGET /repos?org=microsoft|google|apacheGET /repos?org=Adron(a user)not_foundGET /orgsGET /issues(norepo, no default)"Repository required. Set default repo in Settings or pass repo parameter (owner/repo)."GET /issues?repo=o/r&state=allGET /issues?…&state=OPENvalidation_failed— state is case-sensitiveGET /repos/{o}/{r}/assigneesGET /repos/{o}/{r}/labelsGET /repos/{o}/{r}/next-issue-number{"nextNumber":14};1for an issue-less repoPOST /issues, thePATCH, and the comments endpoint were not called — they write to real GitHub repositories.#73 specifically: no client paging needed, but an
?org=isThe epic said "documented as fully paginated; implement paging". Wrong in both directions. The server walks GitHub's pages itself and returns the complete set in one bare array (559 for
?org=github, well past GitHub's 100/page ceiling). There is no envelope, noLinkheader, and nopage/per_pageparameter —?page=2&per_page=5changed nothing. Only?org=exists.But there's an apparent server cap of 2000 (three large orgs each returned exactly 2000;
awsreturned a natural 552), so the repo picker should show a "first 2000" hint rather than implying completeness.Also:
/reposreturns a slim server projection, not GitHub's repo object — exactly{full_name, name, private, owner_login}, uniform across all 2837 items checked.Conversely, issues / labels / assignees are stuck on GitHub's first 30 with no way to page further. That's a real limitation for #75.
#76 specifically:
?link=trueis load-bearing/api/auth/github/authorizerequests onlyscope=user:email read:user.?link=trueis what requestsrepo read:org— i.e. the Issues scope. A?scope=of your own is ignored, and an arbitraryredirect_uriis rejected.Separately,
/api/auth/github/statuscarriesmanageOrgAccessUrl— the documented fix for missing org repos that a reconnect cannot solve (org-level third-party app approval). #76 should surface that as a distinct action, not just "reconnect".#74/#75: pull requests arrive as issues
12 of 13 items from a real repo with
state=allwere pull requests.GitHubIssue.IsPullRequesthandles it — filter or label them, or a GitHub-backed list will silently fill with PRs.Adron commentedon Sep 16, 2026
Implemented in #175 — work continues in the PR from here.
The GitHub-backed tab ships as a self-contained
NewListTabscontrol (5 lines of hosting in the contendedListsView.xaml, nothing added toListsViewModel), with the repo picker, title-defaults-to-repo-name, parent list, Public toggle, and a GitHub badge on backed lists fed by a one-request index. Two of the issue's premises turned out wrong live:/api/github/reposneeds no client paging (the whole set arrives in one bare array) but does need an?org=, and exactly 2000 rows is a server truncation — now confirmed on six large orgs, so the picker says "first 2,000" rather than implying completeness."Detect the missing Issues scope up front" can't be met literally: no endpoint reports scopes, so the panel says so plainly and instead gates on real link state from
/api/user/identities, keeps the reconnect handoff always visible, and distinguishes "reconnect" from "grant organization access". The GitHub-backed create itself was deliberately never executed — it would wire a real repository to a real list — though its 400 contract was verified without creating anything.merge origin/main into issue-73-github-backed-list, and consolidate c…
Merge pull request #175 from CompositeCode/issue-73-github-backed-list