-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
Doesnt work with Obsidian 0.9.10? #7
Comments
Please open a console ( |
@tiagooliveira5n I don't see the actual error on the sshot, it should be above. But please do try going to your vault directory from command line and reinitalizing repository there. In the command line:
|
Hello @denolehov , I reinstalled git and obsidian, however it didn't work. I use Obsidian collaboratively with one more person. In this way, not all files in the vault are "shared", just notes from a specific folder. Probably the error is there, because my repository was configured for a folder inside the vault and not in the vault itself. I'm going to reconfigure the repository so that it synchronizes the vault completely, because I believe that the plugin should look for the .git folder inside the vault. But a detail, reinstalling a "clean" obsidian, unfortunately obsidian-git does not appear in the plugins part (on the bottom left). As print below: |
Heyy @denolehov , it's working! I reconfigured git so that the repository was the full vault. |
I just noticed that the plugin attempted to push, and the error message in the toast had the correct repo name. So I think this may have something to do with the repo being private or the plugin not using the correct ssh key. The required key is located in ~/.ssh, but it is not ~/.ssh/id_rsa, it has another name. |
Sorry, problem was on my end. I had a general mess of ssh keys, some of which were in my keyring and some werent. |
@ljantzen I am glad you were able to figure out the problem! Yeah, having many SSH keys might get messy 😄 |
@tiagooliveira5n oh, I understand your problem! Yes, plugin assumes that root of the vault is the repo itself, I honestly didn't even consider this use-case before, but now that you mention it - I think it'd be a good idea to allow specifying a custom path to git repo within obsidian vault. I will add a note to myself to investigate how this could be achieved. |
As with the calendar plugin there seems to an issue with the plugin not working on version 0.9.10. There is no gui for configuring the plugin, no commands in the command palette.
The text was updated successfully, but these errors were encountered: