Extension Icon

PR Canary

Your open PRs with one-key access to the preview URL that CI posts as a PR comment
Overview

PR Canary

Lists your open GitHub pull requests and opens the preview environment ("canary") that your CI posts as a PR comment, with the arrow keys and Enter.

My PR Canaries

Requirements

  • A GitHub account with access to the repository.
  • A CI job that comments the preview URL on the pull request.

The extension reads your pull requests and their comments through the GitHub API. On first run it asks you to sign in with GitHub (repo and read:org scopes). If your organization restricts third-party OAuth apps, set a Personal Access Token instead (see below).

Setup

PreferenceDescription
RepositoryThe GitHub repository, as owner/name.
Canary URL PrefixOpens the newest URL in a PR comment that starts with this prefix, e.g. https://dashboard.. Leave empty to use the URL that follows a label such as Canary available at:.
Extra Link URL PrefixOptional. A second link to pull from the same comments, e.g. your deploy dashboard.
CI Comment AuthorOptional. The GitHub login of the account that posts the preview URL, e.g. your CI bot (platform-handler). Only comments from this account are used, so nobody else can plant a link. If empty, comments from bot accounts and from repository owners, members and collaborators are used.
Personal Access TokenOptional. Used instead of the GitHub sign-in. Needs read access to pull requests (classic tokens: repo). Stored in Raycast's preferences.

Actions

Press ⌘K on a pull request to see them all.

Actions

ActionShortcut
Open Canary↵
Open Pull Request⌘⇧P
Open Extra Link⌘⇧A
Copy Canary URL⌘C
Refresh⌘R

Troubleshooting

  • "…is not visible" error: the token can't see the repository. Check the repository name. If GitHub's message mentions SAML enforcement, authorize the token for your organization (GitHub → Settings → Tokens → Configure SSO). If you signed in with OAuth, an organization owner may need to approve Raycast for the organization, or you can use a Personal Access Token instead.
  • A pull request shows "no canary": no trusted comment on it contains a matching URL yet. Check that your CI has posted it, that Canary URL Prefix matches, and, if several bots comment, set CI Comment Author to the one that posts the preview URL.
  • Empty list: only open pull requests authored by you in the configured repository are shown.