Repository navigation
docs: 说清真实的依赖布局与「本仓库 main 会进内核 CI」 - #4
Merged
Merged
Conversation
CONTRIBUTING 里「本工作区无法独立安装」那节已经过时：现在 pnpm-workspace.yaml 用 `link:../StackPanel/packages/*` 覆盖，前提是内核并排检出并已构建 spec/sdk/ui/net-guard， 由 `pnpm dev:setup` 校验。 同时补两条实测踩到的约束： - 插件前端是独立工作区项目，只有 `build: tsup`、没有 `prepare`，全新 clone 里没有 `frontend/dist`；只抄 manifest 不抄产物，内核会判定该包「未就绪」。 - 内核 CI 现在会在 Test 前克隆本仓库默认分支并安装 referral/ticket/invoice（否则那 几个套件会 skip，CI 绿但没覆盖），所以本仓库 main 构建坏了会表现为内核 CI 红。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
配套内核 PR #24 / #25。
改了什么
CONTRIBUTING.md两节：「本工作区无法独立安装」→「依赖并排的内核检出」：原文给的两种准备依赖的方式
与现状不符。实际机制是
pnpm-workspace.yaml里的link:../StackPanel/packages/*（外加zod，保证跨边界只有一个 schema 实例），前提是内核并排检出、已
pnpm install、且 spec/sdk/ui/net-guard 已构建；pnpm dev:setup会校验这些前置条件。「提交前必须通过」：补
frontend的单独构建，并说明两个实测约束 ——build: tsup、没有prepare，全新 clone 没有frontend/dist；只抄 manifest 不抄产物，内核会判定该包「未就绪」（
/ready503 且pendingFrontends里是它）。referral/ticket/invoice，再跑内核侧集成测试。本仓库
main构建坏了，表现是内核 CI 红；本仓库自身只有 i18n 门禁，没有完整 CI。