Skip to main content
Use this page when a repository mirror cannot be created, cloned, fetched, pushed to, or accessed by the expected users.
Your entire binary may be older than the repository mirror commands.Update Entire from the updating guide, then try again:
entire repo mirror create github.com/OWNER/REPO
Confirm that the Entire GitHub App is installed and allowed to access the repository.
  1. Open GitHub installed apps.
  2. Find Entire.
  3. Click Configure.
  4. Choose All repositories or select the repository you want to mirror.
  5. Save the GitHub App configuration.
For the full GitHub App setup flow, see GitHub App Access.
Check both access requirements:
  • The Entire GitHub App can access the repository.
  • The user has access to the repository in GitHub.
  • The user has signed in with the Entire CLI using entire login.
After those are true, the user can create or join the mirror:
entire repo mirror create github.com/OWNER/REPO
Entire syncs GitHub collaborators into mirror access hourly. If the user recently got GitHub access or recently signed in to Entire, wait for the next sync or have them run entire repo mirror create github.com/OWNER/REPO.See Mirror Access and Permissions for GitHub-synced access, hourly collaborator sync, and self-onboarding.
The default create command waits for the initial GitHub-to-Entire clone to finish. Large repositories can take longer.If you only need to register the mirror and check back later, use --no-wait:
entire repo mirror create github.com/OWNER/REPO --no-wait
First, confirm you are using the entire:// URL printed by entire repo mirror create.
git clone entire://aws-us-east-2.entire.io/gh/<owner>/<repo>
If the URL is correct:
  • Run entire login to refresh your Entire session.
  • Confirm you have GitHub collaborator access to the repository.
  • If your GitHub access changed recently, wait for the next hourly collaborator sync.
  • Confirm your network can reach the Entire cluster host in the URL.
  • If you added the mirror to an existing checkout, run git remote -v and confirm the remote URL.
Pushes through a mirror are still authenticated with GitHub.If a push is rejected:
  • Confirm the user has write access to the GitHub repository.
  • Confirm branch protection rules and required checks allow the push.
  • Confirm the Entire GitHub App can access the repository.
  • Refresh the user’s Entire login.
entire auth logout
entire auth login
Branch names that start with entire/unmirrored/ are intentionally never synced to GitHub. The branch exists only in the Entire region you pushed it to.To publish the work on GitHub, push the commits to a branch name outside the prefix:
git push origin "entire/unmirrored/<branch>:<branch>"
See Unmirrored branches for how unmirrored branches work.
Removing GitHub access prevents push-through writes because pushes are authenticated with GitHub. Clone and fetch access may continue until the next hourly collaborator sync.See Mirror Access and Permissions for the offboarding flow.
Removing a server-side mirror placement does not edit local Git configuration.Check the remote in the local checkout:
git remote -v
To switch back to GitHub:
git remote set-url origin [email protected]:<owner>/<repo>.git
Include these details when asking for help:
  • entire version
  • the GitHub repository URL
  • the entire:// mirror URL
  • whether the Entire GitHub App can access the repository
  • whether the issue happens during create, clone, fetch, or push
  • the full error message
You can file an issue at github.com/entireio/cli or ask in the Entire Discord.

​
Continue with

Mirrors

Learn how mirrors make GitHub repositories available in Entire.

Mirror Access and Permissions

Understand GitHub-synced access, hourly collaborator sync, and offboarding.