Check GitHub pull requests and Actions on Mac

What you can check from your Mac

MakerNotch shows open pull requests and recent GitHub Actions runs for the repository connected to your selected project. A quick check helps you decide whether to keep working, review a pull request or investigate a failed run.

For example, after pushing a change to Orbit, open the GitHub view and check the latest run. If it failed, open that run on GitHub for its logs. If it passed, check the Vercel deployment before assuming the change reached production. Orbit is an example project, not a customer result.

Choose a pull-request inbox or a project dashboard

Start with the check you repeat most often. If you mainly need a queue of pull requests awaiting your review across repositories, compare a dedicated PR app. For example, PullBar describes configurable pull-request views, while GitHubBar focuses on review requests and review state. These are product descriptions, not a hands-on comparison.

MakerNotch fits a different workflow: select one product, check its repository and CI, then check that product’s deployment and payment connections in the same panel. It connects one GitHub repository per MakerNotch project; it does not combine every repository into a review inbox or provide an inline code-review editor.

Your next question	Where to continue
Is the pull request ready to investigate?	Check its status, then open GitHub for the diff and discussion.
Did the change reach Production or only Preview?	Check the connected Vercel deployments.
Am I looking at the right product’s accounts?	Separate your project connections.

Watch the app tour to see whether this sequence matches your work before buying.

Connect an existing GitHub repository

You need an activated copy of MakerNotch on macOS 14 or later and access to the repository. Follow the installation guide if you have not installed the app.

1. Select the MakerNotch project you want to configure and open Settings → GitHub.
2. For a public repository, enter owner/repository. A token is optional for this route.
3. For a private repository, create a fine-grained personal access token in GitHub. Select the appropriate resource owner and restrict access to the repository you need. Give Metadata, Pull requests and Actions read access.
4. Paste the token into MakerNotch. Use Load repositories to choose a repository, or enter its name.
5. Select Verify and connect. Read the individual checks, then open the GitHub view to confirm the repository and returned data.

GitHub may require organisation approval before a token can access its repositories. Follow GitHub’s token guidance if access is pending or restricted. Use an expiry you can maintain; replace an expired token in the connection settings.

For the optional commit activity map on a private repository, also enable Contents: read. GitHub requires that permission for the list commits endpoint. MakerNotch treats commit history as optional: pull requests and CI can still load if commit access is unavailable. An empty activity map alone does not prove that no commits were made.

A fine-grained token belongs to one resource owner. When projects belong to different GitHub owners or organisations, configure each MakerNotch project with a token for the appropriate owner. The token cannot grant access beyond what its creator already has.

This setup is for reading an existing repository. You do not need repository-creation permissions to monitor it. The optional New repository action is a separate operation.

Refresh frequency and what the status means

Automatic refresh is off by default. You can refresh manually or enable automatic refresh in settings. With it enabled, GitHub checks are approximately every minute while the panel is open and every five minutes while closed. Public access without a token uses approximately three minutes while open.

These intervals can lengthen after errors, during Mac sleep or when GitHub asks the app to wait. A successful workflow means that workflow passed; it does not establish that the deployed application is healthy.

Fix missing pull requests or CI runs

• Repository cannot be found: check owner/repository, the token’s selected repositories and any organisation approval requirement.
• Pull requests load but CI does not: check Actions: read and the warning in the connection checks. MakerNotch can retain pull requests while CI remains unavailable.
• Commit activity is empty on a private repository: check Contents: read and compare with the default branch on GitHub. This is separate from Actions: read.
• No workflow history: confirm the repository actually has GitHub Actions runs. An empty list is different from a failed run.
• Data is old: check whether automatic refresh is enabled, then inspect the connection error. If rate-limited, wait before refreshing again.

The GitHub workflow-runs API documentation explains the read permission used for CI access.

Common questions

Can I use different GitHub accounts for different projects?

Yes. Configure each MakerNotch project with a token that can read its repository. See how to separate project connections. Opening GitHub in the browser still uses the browser’s signed-in account.

Where is my token stored?

In the macOS Keychain for that MakerNotch project. Requests go from your Mac to GitHub. See the privacy policy for the app, licensing and website details.

Can I review or merge a pull request here?

Use the app to spot what needs attention, then open GitHub to inspect the diff, comment or merge.