refined-github/refined-github

`pinned-issues-update-time` broken

Closed

#9,312 opened on Apr 30, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (1,423 forks)batch import
bughelp wantedsmall

Repository metrics

Stars
 (22,918 stars)
PR merge metrics
 (Avg merge 1d 18h) (44 merged PRs in 30d)

Description

Description

It should say "updated" right?

Error: GraphQL:
Could not resolve to an Issue with the number of 0.
    at Object.v4uncached (chrome-extension://jialghbnladbdlhaibaoejjlnihkmemc/assets/github-helpers/api.js:330:9)
    at async CachedFunction.updater (chrome-extension://jialghbnladbdlhaibaoejjlnihkmemc/assets/features/pinned-issues-update-time.js:14:24)
    at async getSet (chrome-extension://jialghbnladbdlhaibaoejjlnihkmemc/assets/npm/webext-storage-cache-cached-function.js:20:32)

How to replicate the issue + URL

https://github.com/refined-github/refined-github/issues

Extension version

26.4.28

Browser(s) used

chrome

Token ⚠️

  • I set a token in the options page. I understand that some features require a token to work.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.