A GitHub token for one repository only
PocketCrew needs to read and write one repository: your office. A fine-grained personal access token can be limited to exactly that, so the app never gets access to your other repositories.
Open the token page from PocketCrew
Press Create the token. GitHub's new fine-grained token page opens with the name, description, Contents: Read and write and a 366-day expiry already filled in.
Choose Only select repositories
Under Repository access, choose Only select repositories, then search for your office repository (its name starts with office-) and tick it. This is the one choice GitHub does not let a link fill in.
Check the permission
Under repository permissions, Contents should be Read and write. GitHub adds Metadata (read-only) by itself. Nothing else is needed.
Generate and paste the token
Press Generate token and copy the value that starts with github_pat_. Paste it into PocketCrew and press Connect.
If something goes wrong
- "Can’t access the repository"
- The token points to a different repository, or the office repository was not created yet. Make a new token and pick the name PocketCrew shows.
- "Your token doesn't have access to this repository"
- Usually Contents was set to Read-only. Make the token again with Read and write.
- "Your token no longer works"
- It expired or was revoked. Make a new one and use Enter token again. Your office and crew stay as they are.
- "You’ve hit GitHub’s request limit"
- This is not a token problem. Wait for the time shown and try again.
The token is stored only in your browser. A classic token with the repo scope would reach every repository on your account, which PocketCrew does not need.
Ready for your own office? Get PocketCrew
Try the free demo →