Obsidian

Connect your Obsidian vault and June can look things up in your notes, add to a note, file a meeting summary or start a new page, in the vault itself. The vault has to live in a GitHub repository.

Keep your vault in a GitHub repository. Most people use the community plugin obsidian-git, which commits and pushes your changes a few seconds after you stop typing and pulls before it pushes. Turn it on on every device you write from.

On the Integrations page, open the Obsidian card and connect GitHub with the GitHub account that can push to the vault's repository. GitHub sends you straight back.

Pick the repository, and the folder inside it if the vault is not at the repository's root, then connect the vault. June checks that your account can push to it before it saves anything.

What June can do

June copies the vault into its sandbox, edits the notes, commits under its own name and pushes to the branch that was your repository's default when you connected. Your history shows which changes are June's. It never rewrites history and never force-pushes.

June's copy holds your notes and other text files; it leaves out plugin settings, images, audio and video, and fetches one of those only when it needs it.

When you both edit

You and June are two writers on one repository. Both pull before pushing, so edits to different notes simply interleave.

If you both change the same lines of the same note before either of you pushed, June does not overwrite your version. It puts its change on a branch named june/ followed by the time, tells you in the chat, and leaves your branch as it is. You decide what to keep.

What June does not do

• It works only with vaults on GitHub.
• One vault per account.
• It uses your vault only in your own chats and projects, not in an organization's chats (why).
• Its edits reach your devices through git: a device that has not pulled yet does not show them.
• A vault in a GitHub organization that restricts third-party apps needs that organization's approval for June first.