docs(contributing): PR 合并顺序与发布流程权威说明 (SHA-10) - #49
Open
WardLu wants to merge 1 commit into
Open
Conversation
Growth Loop MVP 期间多条 PR 相互依赖,把合并顺序、叠加栈去重说明与 合并门槛写进 CONTRIBUTING.md,作为随代码版本化的权威源。
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
摘要
在
CONTRIBUTING.md增补「PR 合并顺序与发布流程」一节,把 Growth Loop MVP 期间的合并顺序作为随代码版本化的权威源(第 1 层),不再只散落在协调任务 SHA-4 的评论与 metadata 里。关联:SHA-10 / 父任务 SHA-4。
变更内容
feat/email-templates) 与 feat(supabase): 共享 Supabase 本地测试路由(拆自 PR #40) #48 (feat/shared-supabase-routing) → SHA-4 Growth Loop MVP 集成:合并 codex/growth-loop-mvp 到最新 main (SHA-5) #43 (feat/growth-loop-integration) → SHA-7 补齐 W2 缺口:期初积分 RPC 与学习包模块启停配置 #44/feat(sounds): W4 五类固定程序化音效与设备级设置 #45/W5: 内测批次表、F0~F6 聚合与 180 天活动事件清理 #46(基于 SHA-4 Growth Loop MVP 集成:合并 codex/growth-loop-mvp 到最新 main (SHA-5) #43 的 growth-loop 叠加 PR 栈)。growth_loop_*迁移经 Shadow Portal 控制面登记并执行到生产;不做前端先行。验证
npm run checknpm run public:check纯文档改动,不涉及源码、数据库迁移或生产。