-
-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge Conflicts since #68 was fixed. #74
Comments
I can confirm I've been seeing this behavior as well. Thank you for finding the probable cause of an issue I haven't had a chance to track down yet. |
I totally see your point. Will decide me for a solution today and patch a fix. Haven't thought about that. |
Should be fixed now. Let me know if you have further problems. |
Is there a way to try this directly from git as the fix is not released yet? |
Sorry I just totally forgot that. Will do it now! |
New release is out |
Thank you, this fixed it 👏🏾 |
Hey, first of, thanks for creating this extension. I don't use a lot of community plugins, but this one turned out to be indispensable. Great work 👏🏾
Adding the timestamp in the data.json file leads to merge conflicts if obsidian is used on multiple machines and obsidian-git is used to synchronize the vault:
Every obsidian instance will updated the timestamp before pulling and thus create a conflict in that file. It's not that this sometimes happens, it happen consistently every time.
I wonder if
I think all of those would fix this. What do you thing would be the best option?
The text was updated successfully, but these errors were encountered: