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
1.3 KiB
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 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
- Read the active plugin inputs.
plugin_context_pathis the copied plugin folder relative to the project working directory. - Inspect
open-design.json,SKILL.md, and any compatibility metadata in the copied folder. - 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>"}' - Read the JSON response. If
okis true, report the final repository URL and any useful log/validation summary. - If the endpoint fails, report its
message,code, and useful log lines. When authentication is missing, tell the user to rungh 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.