bob plugins¶

Manage Bryan's custom Bob Obsidian plugins from the bob-plugins repo.

The list subcommand is read-only: it reads each plugin manifest from the repo, byte-compares the managed files against the vault copy to report sync state, and reads community-plugins.json to report whether the vault has the plugin enabled. Running `bob plugins` with no subcommand runs list.

Before list or sync analyzes files, the plugins repo is refreshed with a non-interactive `git pull` unless --no-pull is given. Pull failures warn and continue with the existing checkout.

The sync subcommand deploys the repo into the vault: it copies the managed files (manifest.json, main.js, and styles.css) from the repo into the vault plugin folder, never touching data.json or other runtime files. It refuses to overwrite a vault file that has uncommitted changes in the vault Git repo unless --force is given. For files that would change, sync prints a diff, and every overwritten vault file is backed up before it is replaced.

Usage: bob plugins [OPTIONS] [COMMAND]

Commands:
  list  List Bob plugins with repo version and vault sync state (default)
  sync  Deploy repo plugin files into the vault
  help  Print this message or the help of the given subcommand(s)

Options:
  -b, --bob-dir <DIR>
          Bob vault root; defaults to BOB_DIR or ~/bob

  -f, --format <FORMAT>
          Output format: table or json

          [default: table]
          [possible values: table, json]

  -n, --no-pull
          Skip 'git pull' on the plugins repo before analyzing

  -r, --repo <DIR>
          Plugins repo root; defaults to BOB_PLUGINS_DIR or ~/projects/github/bobs-org/bob-plugins

  -h, --help
          Print help (see a summary with '-h')

Examples:
  bob plugins
  bob plugins list
  bob plugins list -f json
  bob plugins sync --dry-run
  bob plugins sync --no-pull --dry-run
  bob plugins sync -p bob-project-tasks