Skip to content

ci: validate upstream PR #218 at 9c5fdb9 with the original workflow - #1

Open
lilongsky wants to merge 4 commits into
ci/pr218-base-1b06308from
ci/pr218-head-9c5fdb9
Open

lilongsky wants to merge 4 commits into
ci/pr218-base-1b06308from
ci/pr218-head-9c5fdb9

Conversation

@lilongsky

Copy link
Copy Markdown
Owner

Run the unmodified .github/workflows/pr.yml for upstream magpie-community/plugins#218, which is awaiting maintainer approval for fork workflows.

  • Head: 9c5fdb90e5f5ba7a91e6f49d92bc8aed528c7b7f (same commit as upstream PR kimi-work 0.1.11: renew membership tokens and show shared monthly quota magpie-community/plugins#218)
  • Base: 1b06308fad9386171c25f377d3ff8fcc4d4f3757 (same current upstream base)
  • Both test branches pin existing commits; no code or workflow change is introduced by this test PR.
  • Expected original jobs: test (isolated-HOME full Bun tests and bun scripts/check.mjs) and on-npm (scripts/new-to-npm.sh). No publishing workflow is requested.

After both original jobs pass, attach this run's URL, full commit SHA and results to upstream magpie-community#218 as supplemental fork CI evidence. It does not approve or replace the upstream workflow. This test PR must remain unmerged.

中文:为上游 magpie-community#218 运行原始工作流。固定相同的 head/base 提交,不修改插件代码或 CI;运行完整测试、接口检查和 npm 包状态查询。通过后将运行链接、完整 SHA 和双语结果附到上游 PR,明确标注为 fork 补充验证。本测试 PR 不合并,不触发发布,不涉及本机配置、会话或真实凭证。

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