DocsSettings
Accounts
Connect GitHub or GitLab in Settings › Accounts to see pull requests. Each token is kept in your macOS Keychain.
Open the Accounts tab
Press ⌘, or choose Whaatcher › Settings…, then click Accounts.
Add a server
Under Add a Server:
- In Kind, choose GitHub or GitLab.
- Server starts with github.com or gitlab.com. For GitHub Enterprise Server or a self-managed GitLab, enter its address. In your repositories suggests hosts your repositories use; click one to fill it in.
- Paste a token into Token and click Add.
The address must use HTTPS, because Whaatcher doesn't send a token over plain HTTP. You can add one server per host.
Create a token
Create a personal access token on your server with these permissions, also shown under Token:
- GitHub fine-grained token: Pull requests, Issues, Metadata, Checks and Commit statuses, all read-only.
- GitHub classic token:
repofor private repositories, no scope for public ones. - GitLab: the
read_apiscope.
Whaatcher uses only the tokens you add here, not those of other tools such as the GitHub CLI.
Check the connection
Whaatcher checks a server when you add it and when you click Check. A working token shows Connected as with your login; otherwise the row says why, such as a rejected token.
The result lasts until you quit. After a relaunch the row reads Not checked since launch until you check again or open Pull Requests for a repository on that server. Your own sections in Pull Requests need the login this check finds.
Each row also counts the open repositories whose remote URL points to this host. A remote that uses an SSH alias host doesn't match.
Replace a token or remove a server
When a token expires, click Replace Token, paste the new one into New token and click Save. Whaatcher stops requests made with the old token and checks the new one.
Remove asks first, then deletes the token from the Keychain, stops the server's requests and deletes the pull request data kept from it on this Mac.
Where tokens are kept
Tokens are stored only in your macOS Keychain. The server list keeps only each server's kind and address. If macOS asks whether Whaatcher can use a keychain item, see Install Whaatcher.
What Whaatcher asks the server
Whaatcher sends requests only over HTTPS, only to the servers listed here, and only about repositories whose remote host matches. It reads pull requests with their reviews, review comments, checks, merge state, timelines, commits and linked issues, plus your login. It doesn't comment, approve or merge.
The note under Add a Server lists what Whaatcher sends, and Data and privacy covers every request the app makes.
Without an account
Connecting a code host is optional. Without a server, Pull Requests in Graph only asks you to add one here. Once it's added, pull requests also appear in the commit panel in Graph and in a line's history in Files. Supported agents and hosts lists what works on GitLab.