Private Repos Are Now Supported

What Changed

When you sign in with GitHub, GetPagemark now stores your OAuth access token securely. This token is used during the build step to clone private repositories.

How It Works

The flow is transparent:

1. You select a private repo during site creation
2. We inject your token into the git clone URL
3. The token is used only for the duration of the clone operation
4. It is never exposed in logs or build output

That's it. No SSH keys to configure. No deploy tokens to manage.

What You Can Build

This means you can now use GetPagemark for:

• Internal documentation — company wikis and onboarding guides
• Private project docs — documentation for projects that aren't open source
• Client-facing docs — hosted from private repos, visible at a public URL

Read More

• Why We Built GetPagemark — the story behind GetPagemark and why we made it
• Markdown Is Enough — why plain markdown covers 90% of documentation needs

Security Details

Your token is handled carefully:

Detail	How It Works
Storage	Encrypted in our database
Scope	Limited to permissions you granted during GitHub OAuth
Revocation	Revoke anytime from your GitHub settings
Usage	Only during the clone step — never stored in build output

Availability

Private repo support works on both free and paid plans. No restrictions, no upsell.