我正在从不同的分支切换，所以我可以做一个推送。在进行结帐时，文件在我的编辑器中打开，这可能会导致权限被拒绝错误。git 丢失了我的所有文件吗？我不知道如何让他们回来。这是我所做的——丢失的文件是 js/Messages目录 templates/Messages目录当我做 git 操作时，这些在我的编辑器中是打开
C:Users***Documentsmyproject>git pull
Password for 'https://********@bitbucket.org':
Already up-to-date.
C:Users***Documentsmyproject>git checkout paymentmodule
error: cannot stat 'www/js/Messages': Permission denied
error: cannot stat 'www/js/Messages': Permission denied
error: cannot stat 'www/templates/Messages': Permission denied
C:Users***Documentsmyproject>git checkout paymentmodule
Switched to branch 'paymentmodule'
C:Users***Documentsmyproject>git push origin paymentmodule
Password for 'https://******@bitbucket.org':
To https://*******@bitbucket.org/********/myproject.git
! [rejected] paymentmodule -> paymentmodule (non-fast-forward)
error: failed to push some refs to 'https://********@bitbucket.org/********/myproject.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
//THIS STEP WAS A MISTAKE
C:Users***Documentsmyproject>git fetch origin paymentmodule
Password for 'https://********@bitbucket.org':
From https://bitbucket.org/***********/myproject
* branch paymentmodule -> FETCH_HEAD
//This was what i wanted to do so I did it without reverting my previous step
C:Users***Documentsmyproject>git fetch origin paymentmodule:tmp
Password for 'https://**********@bitbucket.org':
From https://bitbucket.org/*******/myproject
* [new branch] paymentmodule -> tmp
C:Users***Documentsmyproject>git rebase tmp
First, rewinding head to replay your work on top of it...
warning: unable to access 'www/templates/Messages/.gitattributes': Permission denied
warning: unable to access 'www/templates/Messages/.gitattributes': Permission denied
warning: unable to access 'www/templates/Messages/.gitattributes': Permission denied
warning: unable to access 'www/templates/Messages/.gitattributes': Permission denied
Applying: Implement chat services
warning: unable to access 'www/templates/Messages/.gitattributes': Permission denied
Using index info to reconstruct a base tree...
.git/rebase-apply/patch:63: trailing whitespace.
For instructions on this, start with the
.git/rebase-apply/patch:586: trailing whitespace.
#
.git/rebase-apply/patch:588: trailing whitespace.
#
.git/rebase-apply/patch:613: trailing whitespace.
.git/rebase-apply/patch:759: trailing whitespace.
warning: unable to access 'www/templates/Messages/.gitattributes': Permission denied
warning: squelched 348 whitespace errors
warning: 353 lines add whitespace errors.
Falling back to patching base and 3-way merge...
error: cannot stat 'www/templates/Messages': Permission denied
error: Failed to merge in the changes.
Patch failed at 0001 Implement chat services
The copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git rebase --continue".
If you prefer to skip this patch, run "git rebase --skip" instead.
To check out the original branch and stop rebasing, run "git rebase --abort".
//This was a mistake too
C:Users***Documentsmyproject>git rebase --skip
C:Users***Documentsmyproject>git rebase --abort
No rebase in progress?
编辑：
我用以下输出又运行了一个命令。我不确定这意味着什么
C:Users***Documentsmyproject>git fsck --no-reflog
Checking object directories: 100% (256/256), done.
dangling blob 8860babe2931ea1e9dbafaa589e7c4feb19f14c7
dangling commit 1da3053dbe12d11e4ae65dc3a2ba720c9b272b7b
dangling commit cd03cd391e3447be272d3b8307ddb49cd3de1189
dangling blob c9648cae0b45ef174fa88aa5ad6b9008085a9766
dangling blob 2bc76e285d27d6979cf47148711e7c91379910c8
dangling blob 410f4c2f02192a56a9d4c0f01e847d85276799b4
dangling commit 60b1d2f1e2b7f8bfa42d4d2f49857a1b66db8575
dangling blob 949297fe49f427065fe0e74568af852e2796cc19
dangling commit 50d44e0896b10d461629fc5bffe60ee26996d433
dangling commit a8d4aa02b375cb3e04b90033a1a9d17697f6583d
dangling commit f5b5c1a66f450010f30c352caa3baa2f5a3b6576
dangling blob 5af70169556610abe956f748dc25af77494cc06e
dangling blob 981d6a55406d8b2ec63f0952ac65ad1afc893d8a
dangling commit d61db3516d2bbaf24efcf3fe9b644823bdc4a7ff
我必须再次编写整个代码吗！？
在聊天中进行了长时间的讨论后，事实证明您之前的提交(带有日志消息"实现聊天服务"(在 reflog 中仍然可见。(你在问题中说它不是，但你只是错过了它(。所以你需要做的(并且已经做过，正如我从聊天中知道的那样(是：
git reflog
在reflog中大约十行，您将看到"a8d4aa0 HEAD@{12}：提交：实现聊天服务"。所以你需要的提交哈希是a8d4aa0.现在您可以简单地执行以下操作：
git checkout -b new-branch-name a8d4aa0
现在，您的提交在新分支上是安全的，并且可以根据需要进行合并或变基。
顺便说一下，它也可以通过git fsck --no-reflog找到;当你说"不幸的是，这些提交是旧的提交，我认为在我丢失的提交之前就被破坏了"时，你放弃得太早了。以下是您发布的git fsck --no-reflog输出中的行：
dangling commit a8d4aa02b375cb3e04b90033a1a9d17697f6583d
如果你运行了git show a8d4aa02b375cb3e04b90033a1a9d17697f6583d，你就会找到你的提交。
教训：在寻找丢失的提交时，永远不要放弃。永不投降。(谢谢，银河任务！