Replies: 3 comments
|
Update: the failing "only one file change" was caused by our branch being based on an older main; the PR branch has been rebased so the diff now contains exactly one .difypkg. The freshly queued pre-check run awaits approval again — thank you for the help so far! 🙏 |
|
The workflow was approved and all plugin checks are now green ✅ — thank you so much for the quick approval and for pointing the way. PR #3035 is now waiting in the human review queue. Much appreciated! 🙏 |
|
Gentle follow-up: PR #3035 has now been fully green on all automated checks for ~2.5 days (7 days since the original submission). No rush at all — just hoping it is still on someone's queue, since I want to make sure a new comment from us did not accidentally bury the thread. Thank you again! 🙏 |
Uh oh!
There was an error while loading. Please reload this page.
Hi team 👋
I'm maintaining a model provider plugin for the Dify Marketplace (
origin_power_ai, PR #3035) and would appreciate some help with the submission process.What happened
The plugin was first submitted as PR Dify returning information from document that is currently not in the knowledge base but was present earlier #3022 on Sep 4.
pre-check-pluginflagged 3 PR-template issues (missingLocal validation/Security and privacy notessections, non-English body). The PR was closed by a maintainer accordingly.All reported issues were fixed and the plugin was resubmitted as PR FORGET PASSWORD!!!HELPPPPP! #3035 on Sep 8 with a fully compliant description (verified against
dify-marketplace-toolkitchecks — manifestrepo/contactfields, risk level, English-only body).The
pre-check-pluginworkflow run for the resubmission has been inaction_requiredfor over 23 hours (as of this writing) and has not been approved to run. A friendly ping was left on the PR yesterday evening but it may easily get buried in the PR queue.What I'm asking
Could a maintainer (or community moderator) approve the pending workflow run on PR #3035 so the automated checks can execute? The plugin itself already passed everything that ran in the previous round, including the sandbox runtime smoke test (plugin started and served a request successfully).
From the contributor side it is hard to tell whether the approval step is expected to take ~1 week (the documented first-review SLA) or whether waiting longer would still be within normal rhythm — any guidance on the typical cadence for this approval step would also be very helpful.
Thanks in advance for this amazing project and for any pointer you can give 🙏
All reactions