拥有服务器Git仓库直接访问权限时，如何恢复本地未存在的提交？

Great question! You’re absolutely right—if you have direct access to the server-side Git repository, you can recover lost commits that were overwritten or deleted remotely, even if no local copies exist. Let’s break down concrete, real-world scenarios and the exact steps to fix them:

Scenario 1: Remote branch overwritten by a forced push #

This is the most common case: a teammate runs git push -f and overwrites the remote main (or another branch) with an outdated version, erasing recent commits.

Steps to recover: #

1. Log into the server hosting your Git repository, and navigate to the bare repository directory (typically something like /var/git/your-project.git).
2. First, identify all "dangling" commits—these are commits that no branch or tag points to anymore, but still exist in the repository’s object database:

   git fsck --lost-found
   

   This will output hashes for any unreachable commits, trees, or blobs.
3. Inspect each dangling commit to find the ones you need to restore:

   git show <dangling-commit-hash>
   

   Look for commit messages or content that matches the lost work.
4. Once you’ve found the correct commit hash, reset the remote branch pointer back to it. For example, to restore the main branch:

   git update-ref refs/heads/main <target-commit-hash>
   

5. Verify the recovery by checking the branch’s log:

   git log main
   

   You should see the lost commits back in the history.

Scenario 2: Remote tag accidentally deleted #

If someone deletes a critical tag from the remote (e.g., git push origin :v1.0.0), you can restore it directly on the server.

Steps to recover: #

1. Navigate to the server’s bare repository directory.
2. If the server’s repository has reflog enabled (more on this below), you can check the tag’s history:

   git reflog show refs/tags/v1.0.0
   

   If reflog isn’t enabled, use git fsck --lost-found to find the commit the tag pointed to, then inspect commits with git show to locate the right one.
3. Recreate the tag pointing to the correct commit:

   git tag v1.0.0 <commit-hash>
   

   The tag will immediately exist on the remote for all team members pulling from it.

Scenario 3: Remote branch accidentally deleted #

If a branch is deleted from the remote (e.g., git push origin :feature/new-login), you can resurrect it directly on the server.

Steps to recover: #

1. Access the server’s bare repository directory.
2. Use git fsck --lost-found to find the last commit that was on the deleted branch, or check the reflog if enabled to see the branch’s prior pointer:

   git reflog show refs/heads/feature/new-login
   

3. Recreate the branch using the commit hash:

   git branch feature/new-login <last-commit-hash>
   

4. Confirm the branch exists with:

   git branch -a
   

Pro Tip: Enable Reflogs on Bare Repositories #

By default, bare Git repositories don’t track reflogs (the history of branch/tag pointer changes). To make future recoveries easier, enable reflog tracking on the server:

git config core.logAllRefUpdates true

This ensures that every change to branch or tag pointers is logged, making it trivial to roll back accidental overwrites or deletions.

内容的提问来源于stack exchange，提问作者user11680003