Skip to content

docs: publish plugins from CI with API keys - #116

Open
bajrangCoder wants to merge 3 commits into
mainfrom
docs/publish-from-ci
Open

bajrangCoder wants to merge 3 commits into
mainfrom
docs/publish-from-ci

Conversation

@bajrangCoder

Copy link
Copy Markdown
Member
  • New "Publish from CI" guide: creating an API key, publishing with the Acode-Foundation/publish-plugin GitHub Action, and calling PUT/POST /api/plugin with curl
  • Status codes, what keys can't do, and tips for keeping keys safe
  • Links to the guide from "Create new plugin" and the manifest's "Publishing updates"
  • Sidebar entry under Getting Started

@greptile-apps

greptile-apps Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The PR appears safe to merge; the previous finding is fixed and no new issues were found.

Summary

Adds a guide for publishing plugins from CI.

  • Plugin authors now have a guide for publishing releases from CI.

Reviews (2) · Last reviewed commit: "docs: note price changes need the websit..." · Reviewed by Greptile

Comment thread docs/plugin-essentials/manifest.md Outdated
@bajrangCoder

This comment was marked as outdated.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant