✅ Quick Summary
Follow these steps exactly once. After the initial setup, Push44 remembers your token in your browser's localStorage, so you won't need to repeat this for future exports (unless you clear browser data or the token expires).
The Problem
First-time users often aren't sure which GitHub token type to create, which scopes to select, or where to paste it in Push44 — leading to confusing permission errors on the first export attempt.
How Push44 Solves It
Follow these steps exactly once. After the initial setup, Push44 remembers your token in your browser's localStorage, so you won't need to repeat this for future exports (unless you clear browser data or the token expires).
Step-by-Step Guide
Open GitHub token settings
Sign in to GitHub, then go to Settings → Developer settings → Personal access tokens → Tokens (classic) → Generate new token.
Name and scope your token
Give it a descriptive name like 'push44-export'. Set an expiration (90 days is a good default). Check the 'repo' scope box — this grants read/write access to your repositories.
Generate and copy the token
Click 'Generate token' at the bottom of the page. GitHub shows the token once — copy it immediately with the copy icon.
Paste it into Push44
Open push44.vercel.app, go through onboarding or settings, and paste the token into the 'GitHub Personal Access Token' field.
Verify the connection
Push44 makes a test call to the GitHub API to confirm the token works and shows your GitHub username once connected successfully.
Pro Tips
- Set a calendar reminder before your token's expiration date so exports don't suddenly break.
- You can create a Push44-specific token and revoke it anytime from GitHub without affecting any other apps.
Common Mistakes to Avoid
- Closing the token page before copying it — GitHub will not show the value again.
- Pasting a token with extra whitespace — always paste directly without trailing spaces.
Ready to Export?
Push44 is free, open source, and takes under 2 minutes to set up.