Open Pepper-X opened 7 months ago
I have the same issues with you
Same issue. Deleting and cloning again doesn't solve. Not sure why I wasn't having this issue before. The workaround is to checkout the repo first commit, unlock and then checkout main.
git checkout $(git rev-list --max-parents=0 HEAD)
git-crypt unlock
git checkout main
Environment
mac, OS 14.x, git-crypt 0
Background
Somehow the colleague generated the key to me, but when I try to unlock it started show me next errors:
The issue itself
When I had the error above the repository became dirty (had some changes) and if I update the encrypted key (second time encrypted with mt gpg) the unlock did not work for me and said:
But in the same time I could not make
git stash
orgit reset --hard
because I saw this:(In fact I realized that the key was broken somehow, so other colleague generated the key for me - this time all work on newly cloned the repo)
Known way to fix
Thus, I had only way to delete repository and clone it once again. Then the unlock worked even if I update the encrypted (by my gpg) key manually with valid one (secondly encrypted).
Expected behavior
I believe that
git reset --hard
should work in any case - otherwise it seems like a stoppage issue.How to reproduce
This is not real my case, but I reproduced similar issue, so it could help to reproduce and fix this:
git-crypt init
(yeah, it is not correct but it helps to reproduce similar behavior)git-crypt unlock
- done!There is theory (I did not verify that), how to reproduce it once again... Probably 1st time there was additional
git-crypt init
run before adding new gpg user. But I guess this reproducing will also work as well.Summary
the biggest stoppage in that case that
git reset --hard
does not work, but git-crypt we use as tool for git and it seems very strange that git-crypt corrupt whole git repo. Or there is other workaround ? (I looked at this issue-59 but it does not help)