Repository navigation
Fix GitHub push into empty repo - #10
Merged
Merged
Conversation
Pushing to a new repo failed with 'Git Repository is empty' because the repo was created with auto_init:false and ensureMainBranchExists then tried to create a commit from an empty tree, which GitHub rejects on a repo with no initial commit. Create the repo with auto_init:true so main exists, poll until the branch is visible, and pass the existing blob sha when overwriting the auto-created README so the file update does not 409. Verified end-to-end against a live repo (21 files pushed).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Pushing a generated project to a new GitHub repo failed with
Git Repository is empty. The repo was created withauto_init: false, thenensureMainBranchExiststried to build a commit from an empty tree, which GitHub rejects on a repo with no initial commit. The repo was created but no files landed.Fix
auto_init: trueso an initial commit onmainexists.mainbranch is visible (GitHub initializes it asynchronously).README.md), fetch its current blob sha and pass it so the update does not 409.Testing