Entire connects to your GitHub repositories to read checkpoint data. This page covers how to authorize the GitHub App, choose repos, and manage permissions.Documentation Index
Fetch the complete documentation index at: https://docs.entire.io/llms.txt
Use this file to discover all available pages before exploring further.
The Entire GitHub App can read repository contents and write pull request metadata, but it does not write code or modify branches. Checkpoint data is created locally by the Entire CLI and lives on a branch in your repo (
entire/checkpoints/v1); you push that branch yourself with normal git push. See Security & Privacy for the full picture.Authorize the GitHub App
Sign in
Visit entire.io and click Sign in, then Sign in with GitHub.
Land on Entire.io
After authorization you’ll arrive on your Dashboard.
Choose which repositories to connect
After signing in, select which repositories Entire can access.
- Open Repositories in the entire.io sidebar
- Click Configure GitHub App access — this jumps you to GitHub’s app settings
- Select repositories from GitHub’s list, then Save
Permissions
The Entire GitHub App requests these permissions: Repo| Permission | Purpose |
|---|---|
| Administration (read) | Repository creation, deletion, settings, teams, and collaborators. |
| Checks (read) | Checks on code. |
| Commit statuses (read) | Commit statuses. |
| Contents (read) | Repository contents, commits, branches, downloads, releases, and merges. |
| Pull requests (read/write) | Pull requests and related comments, assignees, labels, milestones, and merges. |
| Permission | Purpose |
|---|---|
| Members (read) | Organization members and teams. |
Organization repositories
For repositories owned by a GitHub organization:- An organization admin must install the Entire GitHub App on the organization
- Admins choose which repositories the app can access
- Team members see repositories they have collaborator access to
When you remove access
If you uninstall the Entire GitHub App or remove a repository from its access list:- Entire stops syncing new checkpoints from that repository
- Existing checkpoint data already on entire.io remains visible to team members until you delete it
- The shadow branch (
entire/checkpoints/v1) in your repo is unaffected because Entire did not create or update that branch
Troubleshooting
If sign-in or authorization fails, see Troubleshooting.Continue with
Dashboard
See your activity across all connected repositories.
Troubleshooting
Resolve auth and sync issues.
