The workflow of commit-push is fine, except when you have pending updates in multiple locations. I have two jobs and have to keep things on two different machines for that reason, and I have Logseq open on both to capture information. The commit-push OR pull workflow works fine when I always commit and push before moving from one to the other, but quickly causes the need to rebase when I am not so careful.
One solution is to adopt a commit-pull-push workflow. This is pretty common (see here) and resolves most of the issues folks might encounter. I believe the only change needed is around line 88 of main.tsx, but I am not sure.
One size does not fit all, but from experience, this is the workflow that many of us use for projects generally. I don't know if this could be a configuration option; I am not suggesting cluttering the interface with an additional menu item, just that this helps avoid the need to manually rebase when things go awry.
Love the plugin, use it every day, and keep up the good work!
The workflow of commit-push is fine, except when you have pending updates in multiple locations. I have two jobs and have to keep things on two different machines for that reason, and I have Logseq open on both to capture information. The commit-push OR pull workflow works fine when I always commit and push before moving from one to the other, but quickly causes the need to rebase when I am not so careful.
One solution is to adopt a commit-pull-push workflow. This is pretty common (see here) and resolves most of the issues folks might encounter. I believe the only change needed is around line 88 of
main.tsx
, but I am not sure.One size does not fit all, but from experience, this is the workflow that many of us use for projects generally. I don't know if this could be a configuration option; I am not suggesting cluttering the interface with an additional menu item, just that this helps avoid the need to manually rebase when things go awry.
Love the plugin, use it every day, and keep up the good work!