I’m testing a small script to import old markdown files into Logseq, and as far as I can see there is no real need for most of the steps. Logseq constantly watches the filesystem for changes (logseq/fs_watcher.cljs at 1fd160d9ddea6fab21d6165b0011175285834bfa · logseq/logseq), and when detected they get added to the db.
On my (Linux) system I tested it by adding [[findthislink]] to <logseq-folder/pages/testme.md, on my (active) journal page I add a link by typing [[find it gets completed to [[findthislink]]
In short, in theory nothing should be needed.
If you want to cleanly add a bunch of files to git, this workflow should work:
- Close down Logseq just in case (not 100% needed)
- cd
<logseq-folder> git stash- add markdown files
git add . && git commit -am "added stuff"git stash apply- Now you should be exactly where you left things, with a dedicated commit for your new stuff