Repository navigation
GitHub: repository link, private-repo tag, and Refresh from GitHub #74
Description
Product behaviour (/help/lists)
- The source repository is linked directly under the list name (e.g.
owner/repo issues), opening that repo's issues page in a browser. - A private repo carries a
Private repotag. The tag is about the repository on GitHub, not about who can see the InterlinedList list — the two are set separately. Someone invited to the list may not have repo access, so the tag warns that GitHub will ask them to sign in or show "not found". - Visibility is read from GitHub on each sync (create, Refresh from GitHub, or the scheduled sync), so a repo flipping public/private picks it up next sync. Lists created before the tag existed show no tag until their first sync — an unrecorded value is never presented as public.
Endpoint
POST /api/lists/{id}/refresh — manual refresh for GitHub-backed lists.
Acceptance criteria
-
owner/repolink under the list title, opening in the OS browser. -
Private repotag driven bygithubRepoPrivate, with copy that distinguishes repo access from list visibility. - A null
githubRepoPrivaterenders no tag — never "public". - A "Refresh from GitHub" action calling
POST /api/lists/{id}/refresh, then re-reading the list.
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 #176 — work continues in the PR from here.
The
owner/repo issueslink, thePrivate repotag and "Refresh from GitHub" ship as a self-containedGitHubListHeadercontrol hosted with one line inListsView.xaml.githubRepoPrivateis treated as three states, not two: an explicittruedraws the tag,falsesays "public repository on GitHub", and a null draws no tag at all and explains that visibility is read from GitHub on the next sync — never presenting an unrecorded value as public.The refresh endpoint's rejection path is verified live against a throwaway local list (400 "Refresh is only available for GitHub-backed lists", and inert — the re-read was identical with an unchanged
updatedAt; the throwaway was deleted and confirmed gone). The success envelope could not be observed, since the account owns no GitHub-backed list and creating one would wire a real repository, soListRefreshResultkeeps the raw body and the action re-reads the list rather than trusting it.merge origin/main into issue-74-repo-link-refresh
Merge pull request #176 from CompositeCode/issue-74-repo-link-refresh