[Request] Setup dify-plugins fork and PLUGIN_ACTION secret for automated plugin publishing

Background

The Dify Plugin publishing workflow (dify-plugin-publish.yml) has been merged into the repository. This workflow automates the process of packaging and publishing the AgentCube Dify Plugin to the Dify Plugin Marketplace.

Request

To enable the automated publishing workflow, we need the following setup:

1. Fork langgenius/dify-plugins to volcano-sh
The workflow requires a fork of langgenius/dify-plugins under the volcano-sh organization to push plugin packages and create PRs.

Action Required:

• Visit https://github.com/langgenius/dify-plugins
• Fork to volcano-sh organization
• Expected result: https://github.com/volcano-sh/dify-plugins

2. Configure PLUGIN_ACTION Repository Secret
The workflow uses a secret named PLUGIN_ACTION to authenticate with GitHub for:

• Pushing branches to volcano-sh/dify-plugins
• Creating PRs to langgenius/dify-plugins

Action Required:

• Create a Personal Access Token (PAT) with repo permissions
• The token must have write access to volcano-sh/dify-plugins
• Add it as a repository secret named PLUGIN_ACTION at: https://github.com/volcano-sh/agentcube/settings/secrets/actions

Workflow Trigger

Once configured, the workflow will be triggered automatically when a tag matching dify-plugin/v* is pushed:

git tag -a dify-plugin/v0.0.2 -m "Release Dify Plugin v0.0.2"
git push origin dify-plugin/v0.0.2

Related Files

Workflow: .github/workflows/dify-plugin-publish.yml
Plugin: integrations/dify-plugin/

Questions for Maintainers

• Is it acceptable to fork langgenius/dify-plugins to the volcano-sh organization?
• Can you help configure the PLUGIN_ACTION secret?

Thank you!

Review .github/workflows/dify-plugin-publish.yml first, then inspect integrations/dify-plugin/ to understand the package and tag-triggered workflow. Done means volcano-sh/dify-plugins exists, PLUGIN_ACTION is configured with the required access, and a dify-plugin/v* tag successfully starts the publishing flow.