Connecting GitHub to EverCore
Create a fine-grained token, give it the required permissions, and connect publishing safely.
We will take this one step at a time. You do not need prior experience. By the end of the lesson, you will know exactly what this concept means and what action comes next.
- Why EverCore needs a token
- How token expiration works
- Which repository permissions to select
Why a token is required
GitHub does not allow another app to change repository files without permission. A fine-grained Personal Access Token is a key you create that grants only the access you select. It is not your GitHub password.
Create the token
In GitHub, open Settings, Developer settings, Personal access tokens, and Fine-grained tokens. Create a new token named EverCore. GitHub will show the expiration choices available for your account.
Focus on understanding the purpose of this step. You can return to the details whenever you need them.
About the 30-day message
Some users may only see a 30-day expiration option. That is not an EverCore error. GitHub or an organization policy controls the choices. When the token expires, create a new token and reconnect it.
Repository access
Choose access that includes the repository you created for EverCore. Selecting All repositories is the simplest path when you expect EverCore to create or use additional publishing repositories; selecting only the EverCore repository is more restrictive when supported by your workflow.
Required permissions
Set Administration to Read & Write, Contents to Read & Write, Metadata to Read-only, Pages to Read & Write, and Workflows to Read & Write. These permissions allow repository setup, file updates, GitHub Pages publishing, and deployment workflows.
Copy and connect
Generate the token, copy it immediately, and paste it into EverCore’s GitHub Publishing setup. GitHub may not show the full token again. Never include it in screenshots, messages, or public code.
Test the connection
Use EverCore’s connection test. If it fails, confirm the token is complete, unexpired, tied to the correct account, allowed to access the repository, and configured with every required permission.
What to remember
- The token replaces password sharing with limited, revocable access.
- A 30-day expiration can be normal.
- Never publish or share the token itself.