[Bug]: Gives me an error code when I try to upload, but creates branch on GitHub? #273
Closed
3 tasks done
Labels
🐛 Bug
Something isn't working
Issue validation
Command used
Upload all notes
Plugin version
6.13.1
Describe the bug
Where do I begin? I am sure this is one of these issues where I am having trouble grasping how to use this tool, so let me describe what my intention is.
I would like to configure this plugin to upload notes to a non-default repo. I do not presently have a default repo defined. That is because, like many people, I use Obsidian for many different things, and I would like to isolate my current, desired use of this plugin from future use of this plugin. What I mean is that I would like to use this plugin to upload and host all of my notes for my master's program without making that my default repo for my entire vault.
Here is my issue.
I have not created the repo
mkdocs-template
. Instead, I have defined an alternate repo withshortKey
uiuc
.When I hit "Test Connection," I get the response "Seems Valid!"
However, the bottom bar never accurately reflects the number of files marked for sharing. I am trying to get this to work with just one file.
When I do either "upload all notes" or "upload all notes {project}", I get the following error:
But then when I go to the GitHub repo online, it shows that there is a new branch of my repo with today's date and the files uploaded:
At this point, I'm not sure what to do. All I would like to do is to define the repo via
shortRepo: uiuc
and mark it for sharing viashare: true
, and then I would like for the files to be uploaded and automatically merged withmain
, or preferably committed directly to main. I have "automatically merge" set when I generated the website. I am also not sure why there are 4 "0 Files marked for sharing" fields at the bottom of my screen. All settings are based on themkdocs
preset.How to reproduce ?
No response
Minimal Reproducible Example
Configuration
Relevant log output
OS
IOS
Anything else?
No response
Obsidian information
The text was updated successfully, but these errors were encountered: