✓
the short answer

For classic tokens, always select the full 'repo' checkbox. For fine-grained tokens, explicitly grant 'Contents: Read and write' and 'Administration: Read and write' (if you want Push44 to create new repos) on the specific repository or account.

📖 Introduction

GitHub Personal Access Tokens (PATs) are scoped — meaning a token only has the permissions you explicitly granted it. Permission errors are the single most common reason a Push44 export fails.

The Problem with Walled Gardens

Many users create a GitHub token with default or minimal scopes, then wonder why Push44 can't create a repository or push to a private one. GitHub's fine-grained tokens make this even easier to get wrong.

The Push44 Solution

For classic tokens, always select the full 'repo' checkbox. For fine-grained tokens, explicitly grant 'Contents: Read and write' and 'Administration: Read and write' (if you want Push44 to create new repos) on the specific repository or account.

Step-by-Step Walkthrough

4 steps
1

Go to GitHub token settings

Navigate to github.com/settings/tokens (classic) or github.com/settings/personal-access-tokens (fine-grained).

2

For classic tokens: check 'repo'

Select the top-level 'repo' checkbox, which includes all sub-scopes (repo:status, repo_deployment, public_repo, repo:invite). This is required for private repositories.

3

For fine-grained tokens: set repository access

Choose 'All repositories' or select the specific repo you'll push to. Under permissions, set 'Contents' to Read and write.

4

Regenerate and re-paste

Copy the new token immediately (GitHub only shows it once) and paste it into Push44's GitHub token field, replacing the old one.

Pro Recommendations

✓

Classic tokens are simpler for most Push44 use cases — fine-grained tokens are more secure but require careful scope selection.

✓

Set a token expiration reminder — expired tokens are the most common cause of 'sudden' export failures.

Common Pitfalls to Avoid

⚠️

Selecting only 'public_repo' when pushing to a private repository.

⚠️

Creating a fine-grained token scoped to the wrong repository.

⚠️

Forgetting that GitHub only displays a new token once — losing it means starting over.

Frequently Asked Questions

What's the difference between classic and fine-grained GitHub tokens?

Classic tokens grant broad access based on checkbox scopes (like 'repo'). Fine-grained tokens let you restrict access to specific repositories and specific permissions, which is more secure but requires more careful setup.

Which token type should I use with Push44?

Either works. Classic tokens with the 'repo' scope are simpler to set up. Fine-grained tokens are recommended if you want to limit Push44's access to a single repository.

100% free · zero backend · client-side

Export and push your code in seconds.

Connect your platform, preview the visual diff, and create atomic commits on GitHub with zero server data retention.

Start exporting now → Learn more