Imported from GitHub feature request.

Source issue:

Original context from GitHub:

Right now Tolaria requires creating a new Git repository when opening an existing vault or otherwise refuses to open it. This prevents users from adopting Tolaria with existing notes they created with other tools like Obsidian, and feels like an opinionated constraint that blocks common workflows.

Consider allowing users to open an existing vault directory that does not contain a Git repository. Git integration should be optional in that case. Tolaria can detect whether a vault is already a Git repo and enable Git features, but if not, it should still open the vault normally and offer an explicit, user-initiated option to initialize Git later (or import/pair an existing repo). The default behavior when opening a non-Git vault should be non-intrusive and clearly communicate that Git features are disabled until the user enables them.

This lowers friction for users migrating from other tools or using plain Markdown folders, while preserving existing workflows and files without forcing version control decisions. It would keep the Git integration available for users who want it, while making it an opt-in enhancement rather than a hard requirement.

Additional mention: