fatal: not in a git directory

[supery-chen]

What happened?

after upgrade logseq from v0.6.5 to latest v0.6.6

Reproduce the Bug

1. enable git auto commit
2. upgrade logseq to v0.6.6 on windows10
3. restart logseq

Expected Behavior

no error occured

Screenshots

Desktop Platform Information

Windows10, Logseq v0.6.6

Mobile Platform Information

No response

Additional Context

No response

[cnrpman]

Can you confirm the git integrity in the graph's folder?

[supery-chen]

Yes

[H4M5TER]

I reproduced this on 0.6.7 & 0.6.9
There is .git file on the graph folder contains the gitdir

gitdir: C:/Users/zhuxx/.logseq/git/Fcomma_Logseq/.git

the .git folder is available and I can open the folder manually with GitKraken
This happened after a reboot and still remains with the update.

[H4M5TER]

I tried committing manually on cmdline and encountered fatal: unsafe repository
after doing git config --global --add safe.directory F:/Logseq Logseq is able to auto commit now.

[j0siah]

I tried committing manually on cmdline and encountered fatal: unsafe repository after doing git config --global --add safe.directory F:/Logseq Logseq is able to auto commit now.

This worked for me too.

[cnrpman]

@supery-chen @H4M5TER @j0siah Seems it's related to https://github.blog/2022-04-12-git-security-vulnerability-announced/

[j0siah]

I appreciate the extra details 👍.

[H4M5TER]

Well I encountered the problem again and found my .git file and config under .git folder corrupted
After fixing the .git file and copy the config from a new created graph repo
I can manually add and commit on the cmdline but the issue persisted
Upgrading the Git from 2.36.0 to 2.37.1 and the Logseq from 0.6.9 to 0.7.8 is not work.

[NoEpicLoot]

another windows related pitfall for this error could be caused by the git directory being created from a privileged terminal within an existing graph, in which case logseq (if not running as administrator) is missing permissions to access the git folder