{
  "id": 18506099,
  "title": "GitHub Inbox unread count is missing digits",
  "url": "https://urgent.news/2026/11/06/github-inbox-unread-count-is-missing-digits",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-06T13:14:27.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://nlopes.dev/writing/i-need-the-missing-digits-github"
  },
  "original_language": "en",
  "account": "A long-standing UI issue in GitHub's Inbox feature has garnered attention, with users questioning how it went unnoticed for so long. The Inbox badge correctly displays a seemingly accurate count of two unread notifications, but further down the sidebar, the count jumps to 1,680. This discrepancy raises concerns about the reliability of the notification system.\n\nThe problem lies within the HTML code returned by GitHub's servers, which contains an incorrect value before any scripts are executed or the page is laid out. This flaw is present even before the browser has a chance to run any code or adjust the layout. The issue was confirmed through various methods, including manual verification on mobile devices and querying the notifications API.\n\nUpon examining the JavaScript code, it was discovered that the discrepancy persists even when using GitHub's fetch helper. This suggests that the issue is likely rooted in the server-side code, specifically related to the way the count is calculated and displayed. A likely explanation is that the .to_i method in Ruby is causing the issue. In Ruby, when applied to a number with a comma as a thousands separator (2,240), it returns only the integer value (2), whereas a plain number (2240) returns the full value (2240).\n\nWhile acknowledging that bugs are common in software development, the persistence of this particular issue for years is particularly frustrating. It has led to a lack of confidence in the Inbox badge's ability to provide a clear indication of the number of unread notifications. Users have found themselves ignoring the badge altogether, relying on other means to stay aware of their notifications.\n\nThe question remains: who at GitHub is actually using the product and paying attention to the UI? It is essential for the company to ensure that their own team is fully aware of the user experience and any bugs that may arise. A potential solution could be for a GitHub engineer to either assist in fixing this issue or provide a detailed explanation of why it may be more challenging than it seems.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}