GitHub Ships Pinned Views and a Security Fix to Its Issues Tracker

GitHub shipped a handful of small but welcome refinements to Issues, mostly targeting the friction people run into when they live inside the tracker every day. Nothing here reinvents the workflow, but pinned views graduate to general availability and the dependency REST API gets a security-relevant behavior change worth knowing about.

The shipping list

The headline change: pinning saved views to the repository issues sidebar is now generally available. Saved views let you create custom queries to manage issues across repositories and organizations, and pinning keeps the ones you actually use every day reachable in a single click, even when the sidebar is collapsed.

Four other tweaks shipped alongside it:

• Reaction avatars: Profile avatars now appear on reactions, so you no longer have to hover a thumbs-up to figure out who voted.
• Dashboard density: You can adjust the Issues Dashboard density to see more items at once, and hide closed sub-issues to focus on work that is still open.
• Scoped dependency API: The issue dependency REST endpoints (blocked_by, blocking, and relates_to) now filter results based on the token's granted scope.

The REST change automation teams should read

The dependency endpoint tweak is worth flagging for anyone writing automation. Previously, a token could surface relationship data for issues in repositories it did not have permission to see. Responses now respect the token's scope, so bots, dashboards, and internal reporting scripts return results that match what the caller is actually allowed to view. If you have integrations that walk blocked_by or blocking graphs, expect result sets to shrink for narrowly-scoped tokens and plan accordingly.

Who benefits

These changes are aimed squarely at teams that use Issues as a real project management surface rather than a dumping ground. If you juggle a dozen saved queries like "assigned to me across three orgs" or "P0 bugs in the mobile repo," pinned views cut navigation clicks. If you run big epics broken into sub-issues, hiding closed ones removes visual noise from checklists that are 80% done. Denser dashboard rows help when you are triaging hundreds of issues in a sitting.

Availability and cost

Everything here is live on github.com now and rolls out with your normal GitHub plan at no extra charge. Pinned saved views is out of preview and generally available; the other improvements land as part of the ongoing dashboard evolution that began with saved views. GitHub has opened a community discussion for feedback if any of the density or sub-issue behaviors feel off.

None of this replaces a dedicated project tool if you have outgrown Issues, but the cumulative effect of the past year of dashboard work is that github.com/issues is starting to feel less like a raw list and more like something you can actually run a backlog from.