Repository navigation
fix: limit internal Photo CI handoff to develop - #5359
Merged
Merged
Conversation
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.
本轮新工作流先接入目标分支为
develop的内部新 PR。旧 Photo CI 的跳过条件同步检查 base 分支,避免指向main、dev/*的 PR 被旧 CI 跳过、又被新流程拒绝。未配置启用起点时行为不变;中英日贡献指南同步说明范围。验证:Node.js 22 直接执行 workflow 中的 Bash/Python,31 项边界通过(2 组测试),覆盖 develop、main、dev、大小写、缺失目标、时间、fork 和人工入口。全量视觉测试已尝试,但检出目录缺少 TypeScript/Rush 依赖,在截图前预检失败,不记为视觉通过。同一已提交版本已在 Linux Node.js 22、UID999/GID996、无网络、1 GiB/64 PID/2 核预算下通过两仓共 62 项边界(4 组测试,零跳过)。
本 PR 合入本身不启用新工作流;启用还需服务端和 Bot 同一范围、统一未来起点及首次发现基线。Bot 不自动批准或合入。
维护者启用记录(2026-10-29):已完成接入配置,统一起点为北京时间 17:35(09:35 UTC)。仅起点之后新建、同仓库且目标为
develop的非 Draft PR 接入;新 Draft 转为 ready 后接入。首次存量基线已完成,存量、fork、main/dev 等其他目标不补跑,继续适用旧 CI 的原有触发规则。本交接 PR 创建于起点前,因此运行旧 BugServer CI 符合预期。Photo 保持 report-only,人工核查、Approve 和 Merge,自动基准更新暂停。首个起点后新 PR 的端到端流程及长期稳定性尚未验收。