Add github-navigator extension

[tofrankie]

Description

A lightweight personal GitHub repository navigator.

• Unified repository list: personal (owner), collaborator, and organization repositories in one place
• Flexible sorting: sort by last updated, stars, open issues, or pull requests
• Optional frecency sorting: repositories you open more often and more recently can move higher in the list
• Quick actions: open a repository, issues, pull requests, actions, releases, insights, settings, and dependents; forked repositories also include an upstream action (⌘1 ~ ⌘9)
• Browser tab reuse: optionally focus an existing browser tab instead of opening a new one

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Greptile Summary

Adds a macOS-only GitHub repository navigator extension.

• Lists personal, collaborator, and organization repositories with complete pagination.
• Supports filtering, sorting, frecency ranking, repository actions, and browser-tab reuse.
• Includes extension metadata, documentation, assets, and build configuration.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains in the fixes associated with the previous review threads.

Important Files Changed

Filename	Overview
extensions/github-navigator/src/browser-repository.tsx	Implements the repository list, filtering, frecency tracking, actions, and browser-tab reuse for the now macOS-only command.
extensions/github-navigator/src/graph.ts	Fetches and paginates viewer, organization-membership, and repository GraphQL connections.
extensions/github-navigator/package.json	Declares a macOS-only view command, preferences, dependencies, and standard Raycast extension metadata.

_{Reviews (3): Last reviewed commit: "feat: remove Windows platform" | Re-trigger Greptile}

[tofrankie]

@0xdhrv Request for Review

[0xdhrv]

Thanks for your contribution 🔥

We already have an extension in the Store that covers the same core functionality:

• GitHub Repository Search by @thomaspaulmann

Both extensions provide a fast way to find and navigate GitHub repositories from Raycast, with frequently or previously accessed repositories surfaced for quicker access.

The existing extension already provides:

• Searching GitHub repositories, including personal and organization repositories
• Keeping track of previously visited repositories
• Opening repositories directly in GitHub
• Quick access to pull requests, issues, projects, wikis, and releases
• Opening repositories in a Web IDE or cloning them in VS Code
• GitHub OAuth, PAT, and GitHub Enterprise support

This PR adds some useful capabilities:

• A unified personal/collaborator/organization repository list
• Sorting by updates, stars, issues, pull requests, and frecency
• Additional shortcuts to Actions, Insights, Settings, Dependents, and upstream repositories
• Optional reuse of existing browser tabs

However, these appear to be natural enhancements to the existing repository-search and navigation workflow rather than enough differentiation for a separate extension.

Could we consider contributing the expanded sorting, repository shortcuts, and browser-tab reuse functionality to the existing extension instead?

This would help avoid duplication and keep GitHub repository navigation consolidated in one extension.
As mentioned in our extension guidelines here ↗

[tofrankie]

@0xdhrv

I believe they have different focuses.

GitHub Repository Search searches the entire GitHub repository ecosystem, emphasizing its "search" capability.

My extension, on the other hand, focuses on personal repositories, offering faster and cached queries, displaying all of a user's repositories, and allowing filtering. It doesn't require users to actively search; it aims to make it easier for developers to view the repositories they maintain.

I think it can serve as a new extension with a different experience. GitHub Repository Search will certainly have its audience, and I believe my extension will also have its needs. I understand the platform's concerns, but I think the platform should also support diversity, which is one of the reasons we like Raycast.