I keep a small folder with files I want Orgzly to pay attention to below my main "org-roam" folder (mostly scheduled stuff - like Calendar.org and Todo.org). I

I keep a small folder with files I want Orgzly to pay attention to below my main "org-roam" folder (mostly scheduled stuff - like Calendar.org and Todo.org). I treat them as "read only" on my phone except for "PhoneInbox.org". That is where I add items on the go with Orgzly. At some point I move these out into other org folders (inbox processing). This makes capture into Orgzly very, very fast and using Git keeps it all synched up without issues of file conflicts, etc. Workflow is something like: 1. Sit down at desk, save all agenda files, and do a commit/push (Emacs/Magit) - this is the entire repo including the sub dir with my Orgzly files 2. On phone (Mgit Android app) do a commit/pull 3. Pull down to desk 4. Resolve conflicts (usually none) 5. Do whatever inbox processing on PhoneInbox 6. Redo the commit/push and pull changes to phone. This keeps an entire repo of my org files on the phone for reference but minimizes the number of files Orgzly has to deal with and also reduces conflicts from editing a file in Orgzly and on phone. Sounds onerous but I might do this a few times a week, possibly daily if I am having a busy week.