WeSearch

GitHub Is Having Trouble Counting Things

·1 min read · 0 reactions · 0 comments · 6 views
More from Chuckgreenman programming Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

GitHub is Having Trouble Counting Things Sep 2026 In the past week, I’ve noticed two pretty severe UI bugs in GitHub. The first is an overcounting of PRs in the tab on a repository, this is particularly common after you merge a PR, but it’s not the only trigger of this behavior. To add insult to injury, the right count is even right there on this page.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,731 of its stories. Top-voted stories on Hacker News.

Original article
Chuckgreenman
Read full at Chuckgreenman →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherChuckgreenman
Canonical URLhttps://chuckgreenman.com/2026/09/16/counting-at-github
Publication timeWed, 16 Sep 2026 17:31:19 +0000
Retrieval time2026-09-16T19:08:41.546Z
Last seen2026-09-16T19:08:41.546Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterU1ho-F2qFWOb · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

GitHub is Having Trouble Counting Things Sep 2026 In the past week, I’ve noticed two pretty severe UI bugs in GitHub. The first is an overcounting of PRs in the tab on a repository, this is particularly common after you merge a PR, but it’s not the only trigger of this behavior. To add insult to injury, the right count is even right there on this page. The second occurred while I was trying to set up Sentry. I’ve been using GitHub for 11 years now, so I have collected three pages of org memberships. Unfortunately for me, the project I’m setting up Sentry for is on the second page. For some reason, Chrome doesn’t let you modify the address in the bar for these pop-up windows. Luckily, you can force navigate using JavaScript.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Chuckgreenman.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Chuckgreenman