You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While cloning, I got an error that remote is empty (wow!). I expected the app to push my note and initialize remote with it.
So I created a dumb note via GitHub and successfully cloned the remote.
Now I had two notes in my root folder: the original one and the dumb one.
Of course, the app failed to correctly merge my note and a dumb one in one commit, as far as understood. I tried to delete the note, but it lead only to proliferating new unsynced commit.
So I opened raw mode of my original note, copied to third place, deleted the whole local repository, cloned remote again and only then added my original note and only then it synced correctly
Well, I understand a bit, why all of this happened, the short answer is "because this is how git works", but I think that adding some logical glue to eliminate even a possibility for someone to undertake such a journey would be nice for every newcomer.
The text was updated successfully, but these errors were encountered:
Seeing similar, trying to use the GitHub easy setup and create a repo from scratch but it fails with "Exception: Exception: GitFetch failed with error code: remote repository is empty". Would that be just because I created a local note before trying to set up sync, you think? Did you happen to find any workaround that might help get my issue unstuck too?
Android 14 AFAIK
I did the following:
Well, I understand a bit, why all of this happened, the short answer is "because this is how git works", but I think that adding some logical glue to eliminate even a possibility for someone to undertake such a journey would be nice for every newcomer.
The text was updated successfully, but these errors were encountered: