You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document what the sub-issues endpoints return after a sub-issue's repository is deleted #46960
What part(s) of the article would you like to see updated?
The article doesn't say what the list endpoint returns when a sub-issue's repository has been deleted. In my case the entry stayed in the list, returned to a GitHub App installation token with its title and html_url. A direct read of that issue returned 404, and the parent's sub_issues_summary.total still counted it, one higher than the list I could read with a personal token.
Please document:
whether a deleted repository's sub-issues are expected to stay listed or counted, and for how long
whether the list can return different entries to different token types
how a client should detect and unlink such an entry (for example, what sub_issue_id to pass to the remove endpoint when the issue can no longer be read)
Use case: automation that reads the list and tries to open each issue gets a 404 on this entry and has no way to tell it apart from a transient error.
Additional information
I can reproduce this reliably on one parent issue. It has been listed for weeks after the repository was deleted.
Since the content you've highlighted is solely determined by the API specification, please raise this issue against https://github.com/github/rest-api-description, as that's the right place for such content
Activity
subatoi commentedon Nov 16, 2026
@zolotokrylin Thanks for raising an issue
Since the content you've highlighted is solely determined by the API specification, please raise this issue against https://github.com/github/rest-api-description, as that's the right place for such content
I'm going to go ahead and close this out