Files
wehub-resource-sync 070959e133
landing-page-staging / Deploy landing page to staging (push) Has been skipped
landing-page-ci / Validate landing page (push) Failing after 4s
visual-baseline / Capture visual baselines (push) Has been cancelled
bake-plugin-previews / Bake plugin previews (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:00:47 +08:00

1.3 KiB

name, description, triggers, od
name description triggers od
od-plugin-publish-github Publish a local Open Design plugin to a new public GitHub repository using gh CLI.
publish plugin
github repo
open source plugin
mode platform scenario
utility desktop plugin-sharing

Publish Plugin to GitHub

Use this workflow when the active project contains a copied plugin folder and the user wants it published as a new public GitHub repository.

Workflow

  1. Read the active plugin inputs. plugin_context_path is the copied plugin folder relative to the project working directory.
  2. Inspect open-design.json, SKILL.md, and any compatibility metadata in the copied folder.
  3. Call the local daemon endpoint instead of hand-rolling GitHub commands: curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/publish-github" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'
  4. Read the JSON response. If ok is true, report the final repository URL and any useful log/validation summary.
  5. If the endpoint fails, report its message, code, and useful log lines. When authentication is missing, tell the user to run gh auth login --hostname github.com.

Prefer the manifest name as the repository slug. If that repository already exists, choose the next clear slug and mention the rename.