search

jobindjohn / obsidian-publish-mkdocs

A Template to Publish Obsidian/Foam Notes on Github Pages (uses MkDocs)
Creative Commons Zero v1.0 Universal
524 stars 37 forks source link

Revisions not pushed #21

Closed Tindalos closed 1 year ago

Tindalos commented 1 year ago

Having loaded the repo into Obsidi█n as a vault, and set GitPages to update from 'gh-pages', and GitHub Desktop by default pushing to 'main', revisions do not appear on GitPages after a push.

Alternately, on setting GitHub Desktop to push to 'gh-pages' instead it immediately notices revisions automatically made to files in the '.obsidian' directory. Commit-and-Push is unsuccessful because 1 Pull is pending for 'gh-pages' first due to remote revisions. GitHub Desktop is then unable to Pull either, citing, 'Unable to merge unrelated histories in this repository.'

I've retried anew several times, with occasional success pushing 'gh-pages' after Obsidi█n has added its contribution files to the vault. Upon 'gh-pages' being pushed, the files in the local vault directory are converted into .html files with the result that the original local files, though not the vault's directory structure, are no longer editable by Obsidi█n.

Perhaps I'm missing something very basic here.

[Edit: It's when GitHub Desktop is directed to address 'gh-pages' rather than 'Main' that the Markdown files are replaced with .html. Without directing it to address 'gh-pages' I'm unable to commit and push to GitHub, and when I do the files are replaced by .html and Obsidi█n cannot work with them. What am I missing?]

Tindalos commented 1 year ago

Sorted.

'Main' is the Obsidi█n-editable stuff, 'gh-pages' is the autogenerated content for GitPages. Never shift GitHub Desktop from 'Main' to 'gh-pages', it will overwrite the .MD vault files to .html etc., reducing the local repository version to something which not only can Obsidi█n neither read nor edit, but which GitHub does not recognize as a viable repository.

I had misunderstood, thinking that I'd had set GitHub Desktop to push to 'gh-pages' not only because that's what GitPages recognizes, but also because when I didn't my pushed revisions weren't showing up on the GitPages site. They were, it just takes a few moments for the revisions to be implemented. Leaving this in case it assists someone else encountering the same problem.