You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a user's local git repo becomes too large, git cannot push the changes, and the push fails. Afterward, we do not remove the commit that was created for the push, which means the oversized commit is still in the git history and will prevent any future push calls.
Expected behavior
The git repo should be cleaned after an error. For a failed push we should revert the commit and bring the repo to the same state as it was before the error.
Potential solution: git reset HEAD~1 and git gc
The text was updated successfully, but these errors were encountered:
Describe the bug
When a user's local git repo becomes too large, git cannot push the changes, and the push fails. Afterward, we do not remove the commit that was created for the push, which means the oversized commit is still in the git history and will prevent any future push calls.
Expected behavior
The git repo should be cleaned after an error. For a failed push we should revert the commit and bring the repo to the same state as it was before the error.
Potential solution:
git reset HEAD~1
andgit gc
The text was updated successfully, but these errors were encountered: