feat(github-actions-grafana-jump)!: page-based jump links - every entry is just a name and a URL

[nsheaps-oura]

What this changes

Two things, together, because they only make sense together.

1. Every config entry is now just a link. A name you word however you like, and a URL you write yourself with {{field}} placeholders in it. The type: dashboard / type: trace split is gone, along with the top-level baseUrl and the two URL builders those types fed. A Grafana dashboard link and a Tempo trace link are now both plain URLs — you paste the URL you already have and swap the parts that vary for placeholders.

2. The config is organized by page instead of by guesswork. It used to infer where a link belonged from which fields its URL happened to use. Now the top level is a list of pages, each with its own links, and a link only shows up on the page kind it's listed under.

pages:
  - page: pr
    links:
      - name: CI for this PR
        url: https://grafana.example.com/d/ci/ci?var-pr={{prNumber}}
  - page: branchList
    links:
      - name: CI
        url: https://grafana.example.com/d/ci/ci?var-branch={{branch}}

Where the links actually show up

flowchart TD
    A[Page loads or DOM mutates] --> B{Which kind of page?}
    B -->|PR list, branch list| C[One small link per row,<br/>revealed on hover or focus,<br/>scoped to that row]
    B -->|Has a known toolbar| D{Toolbar found?}
    B -->|No toolbar entry| F[Floating button,<br/>bottom right]
    D -->|yes| E[Primer-styled buttons<br/>in GitHub's own toolbar]
    D -->|no| F

Loading

Previously this was a single hardcoded special case: pull request pages got an inline button, and everything else floated. Now each page kind has its own toolbar selector, and the floating button is the fallback rather than the norm. The old PR selector [class^="gh-header-actions"] was dead — that header is [class^="prc-PageHeader-Actions-"] now.

New page kinds

Six pages had no representation at all before: the repo home page, a file view, the pull request list, the branch list, the Actions tab itself, and a single job within a run. That last one used to be folded into the run page, which is why jobId was an optional field on it; they're separate kinds now.

The two list pages work differently from the rest — instead of one button for the page, each row gets its own link pointing at that row's own PR or branch, revealed on hover or keyboard focus. That's the same mechanism Primer uses for its own trailing row actions (:hover, :focus-within on the row), and it fades rather than hides so the links stay in the tab order.

Also in here

• Fixed: GitHub's React header throws the injected container away. It re-renders without the URL changing, and the buttons never came back (seen live on a workflow run page). Placement is now re-checked on every DOM mutation, and the container's contents carry a signature so re-rendering identical content is a no-op — otherwise the write would itself be a mutation and loop.
• Fixed: the stale comment above CONTAINER_ID still describing the old "PR gets inline, everything else floats" rule.
• The docs can't drift. The page/field reference at the top of .github/jump-links.config.yaml is generated from the code, and a test asserts the file matches. Two more drift tests: every declared page kind has to be reachable from resolveJumpContext(), and this repo's own checked-in config has to still parse with all its links surviving the placeholder gate.
• Storage key bumped to jumpLinksConfig.v2. Nothing reads v1, so an existing personal config is left alone rather than half-migrated into a shape it can't express.

Breaking

Configs in the old targets: format aren't read any more. Repo configs need rewriting in the pages: format; personal configs need re-entering through the config panel. Renaming the package away from its "Grafana" branding is deliberately not in here — that's its own change.

How this was verified

Code-correct: typecheck clean, 58 unit tests passing, build script runs, oxlint clean for this package (the warnings it prints are pre-existing, in other packages).

Live on real github.com pages, with the compiled build injected into the page and a fake config — repo home, file view, PR list, branch list, one workflow's runs, and a run. Buttons landed in the right toolbar with the right text and the right filled-in URLs; per-row hover links appeared on only the hovered row with that row's own PR number / branch name. Not verified live: the pull request page itself (its toolbar selector is unexercised), and the Actions tab's own landing page. A userscript manager is installed in the browser I used, but it runs the released version and I couldn't repoint it at this build, so all of the above was injected by hand rather than loaded as a userscript.

One thing to know before merging: yarn install --immutable already fails on main - the root package.json pins typescript at ~6.0.3 while yarn.lock resolves ~7.0.2. That predates this branch and nothing here touches either file, but it will show up in CI.

Co-Authored-By: Claude noreply@anthropic.com

[github-actions]

Userscript Version Preview

Preview only — versions and CHANGELOGs are bumped automatically on merge to main, not in this PR. Manual bumps to a higher version are preserved.

Package	Base	New	Action
github-actions-grafana-jump	0.2.6	0.2.7	will-bump