Sorry for my delayed response!
No, I don’t believe so. We crossed the “line ending issue” early during adoption and found that Windows implementations needed receive autocrlf=true
in .git/config
. That corrected the line ending problem for us.
The timestamp issue appears to be distinct, and one could argue it’s more of an abnormality with git. This is the first time I’ve witnessed git hit on timestamp changes.
A partner organization uses Obsidian as well and they implemented the workaround shortly after we did.
We’ve not witnessed this issue in 16 days!
Example Workaround Git Configs
Linux
[core]
bare = false
autocrlf = input
Windows
[core]
bare = false
autocrlf = true
trustctime = false