# Obsidian

> June reads and edits the notes in an Obsidian vault you keep in a GitHub repository, through your GitHub connection.

Source: https://www.dearjune.ai/docs/integrations/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.

1. Keep your vault in a GitHub repository. If you use the community plugin obsidian-git, configure it to commit, pull and push regularly on every device you write from. June sees the changes that have reached GitHub.
2. 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.
3. 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.

> Example prompt: What did I write about the pricing experiment in my vault?

> Example prompt: Add today's call with Lena to my meeting notes, with the three action items.

## 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. Review the branch June names in the chat, merge the changes
you want in GitHub, then pull on your devices before continuing to edit.

## 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](/docs/integrations#personal-or-organization)).
- 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.