cgithub.git, branch main

Read the pull request list from embedded JSON

2026-09-25T06:15:25Z

GitHub's pull request list no longer renders .js-issue-row rows server-side; the rows come from the repoPullsDashboardContentRoute payload instead. Co-Authored-By: Claude Opus 5.5

Show each repo nav item only if the GitHub page includes it

2026-09-25T06:15:02Z

Co-Authored-By: Claude Opus 5.5

Style markdown alerts

2026-09-25T05:43:53Z

Co-Authored-By: Claude Opus 5.5

Show issue and pull request status and labels in their lists

2026-09-25T05:43:53Z

Co-Authored-By: Claude Opus 5

Add issue details

2026-09-25T05:43:53Z

Co-Authored-By: Claude Opus 5

Add discussions

2026-09-25T05:43:53Z

Discussions are served from GitHub's older server-rendered HTML, with no embeddedData JSON to read, so the scraper walks the DOM the way the pull request and wiki code does. A discussion's timeline opens with its own post and continues with its comments, each carrying its replies nested inside it, which is where the recursion in _discussionComment.eta comes from. Categories, upvotes, and the answer a Q&A discussion is marked with all come along. Only what GitHub renders up front is shown: neither the next page of discussions nor the replies it hides behind a "Show N previous replies" button are fetched, so a comment says how many replies it is missing. Co-Authored-By: Claude Opus 5

Add favicon

2026-09-22T17:24:31Z

Easier clone command selection

2026-09-21T21:40:15Z

Use base layout for home page

2026-09-21T16:16:34Z

Rearrange search dropdown

2026-09-20T13:39:37Z