It's a collection of independent features, not a single-purpose tool: each one lives in its own folder under features/ and can be added, removed, or shipped on its own. GitHub covers the fundamentals well; this is for the gaps that are easier to fill from the outside than to wait on.
Install
Install GH Reloaded from the Chrome Web Store, then open Settings: click the extension's toolbar icon, or from chrome://extensions → the extension's card → Details → Extension options.
Most features work on public repositories without a token. A token adds private repositories, Projects v2 data and higher rate limits.
Create a GitHub token
Pick one of two supported token types: A (recommended) for most setups, B when your Projects are owned by a personal account.
A. Fine-grained token (recommended)
Go to github.com/settings/personal-access-tokens/new and set:
- Resource owner → the account or organization that owns the repositories (a token has exactly one resource owner).
- Repository access → Only select repositories → pick the repo(s) you want this on.
- Permissions, all Read-only, everything else stays at No access:
| Scope | Permission | Used for |
|---|
| Repository | Issues | sub-issues, dependencies, org-level custom fields (Team / Business Value / Effort), My Issues, confirming a Quick assignment (read-only), Notification reason tags (mentions) |
| Repository | Pull requests (and Commit statuses or Checks for the checks rollup) | PR triage, Linked PR status, Notification reason tags (review requests and mentions) |
| Repository | Contents | HTML preview and Image gallery of files in private repos (public repos work without a token) |
| Repository | Metadata | added by GitHub automatically |
| Organization | Projects | Projects v2 Status, Standup mode, My Issues project memberships |
Click Generate token and copy it immediately — GitHub shows it exactly once.
Already have a token? Notification reason tags needs no new permission, but a token limited to selected repositories shows Unverifiable on inbox rows from other repositories. Open the tag's panel: it names the permission (Pull requests: Read or Issues: Read) and links to Settings → GitHub tokens, where Verify access with one of those repositories shows whether the token can read it.
Two GitHub limitations to know about:
- Organization permissions only appear when the resource owner is an organization. A fine-grained token cannot read Projects owned by a personal account: for those, use a classic token (B). Without it the features that depend on them degrade (no Status, Standup signals or project memberships) while the rest keeps working.
- A fine-grained token has one resource owner, so work across several owners (organizations or personal accounts) needs one token per owner, see Connect it.
If the organization requires approval for fine-grained tokens, the token you create may show as pending until an organization owner approves it, and requests to that organization's data can come back empty or 404 until then, since GitHub doesn't otherwise reveal that the resource exists. If the organization has disabled fine-grained personal access tokens altogether, it does not appear in the Resource owner list and you cannot create a token for it: ask an organization owner to allow fine-grained tokens, or use a classic token.
B. Classic token (Projects owned by a personal account)
Use this when the Projects you want to read belong to your personal account, which fine-grained tokens cannot read. Go to github.com/settings/tokens/new?scopes=read:project,public_repo&description=GH%20Reloaded and tick:
read:project — read access to Projects v2.public_repo — GitHub's GraphQL API requires it for the issue and status data the Projects features read. The extension only reads, but the scope itself is broad: GitHub defines it as read and write access to code, commit statuses, repository projects, collaborators and deployments of every public repository your account can reach.repo — instead of public_repo, only if you also need private repositories (issues, sub-issues, dependencies, HTML preview). Tick it yourself on the same page: it is broad, it also grants write access to every repository your account can reach.
The extension only reads, but a leaked classic token could do more than a fine-grained one, so prefer A whenever it covers your setup, and leave repo off unless you need private data. One classic token covers every owner you can reach, so you do not need one per owner.
If an organization enforces SSO, open github.com/settings/tokens and use Configure SSO next to the token to authorize it for that organization; otherwise GitHub answers with empty results or 404.
Connect it
Back in the extension's Settings page, under GitHub tokens: paste the token (github_pat_… or ghp_…) into Default token, Save tokens, then Test — it should report the GitHub username the token authenticates as.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
