Repository navigation
docs(chapters): 写第五章《PR 与合并权限》并更新路线图 - #14
Merged
Merged
Conversation
覆盖硬规矩二(未经船长明确同意不合并 PR)、yolo 只管合并权限且不改变 质检流水线本身、以及红色 CI 无论 yolo 或船长指示都不能合并;用第一章 交付时的强推插曲与第二、三章的「合并吧」流程作真实案例。README 路线图 第五行标记为已写并链接新章节,章末预告第六章。
…merge claim, section cite
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.
Intent
继续 Learn FirstMate 教程,写第五章。前四章已写完(第一、二章已合入主分支,第三、四章正在走质检流水线)。README 的学习路线图里,第五章的定位是:为什么默认必须船长点头才合并,yolo 姿态放开了什么、没放开什么,以及红色 CI 为什么依然不能合。第五章也是「沿着一件活的真实旅程往下走」这条线(第 2 到 5 章)的最后一章。
What Changed
chapters/05-pr-merge-authority.md:讲清默认必须船长点头才能合并 PR、yolo姿态只放开合并权限而不放开质检标准、红色 CI 在任何设置下都不可合并(仅fm-pr-merge.sh --allow-red可豁免船长当下明确点名的单项检查),并引用本仓库自身 PR 的合并状态作为佐证,附两个只读动手练习。README.md的路线图表格,将第 5 章状态从「待写」改为「已写」并链接到新章节文件。Risk Assessment
✅ Low: Pure documentation addition (new chapter 5 plus a README roadmap link update) with no code, build, or config changes; every behavioral claim traces to AGENTS.md text I verified directly in the local FirstMate checkout, and the PR-status claims about PR #1/#3/#4 match actual GitHub state as of the commit timestamps; the docs check passes.
Testing
This is a documentation-only change (README nav line + new chapters/05-pr-merge-authority.md) in a repo explicitly defined as having no build system, dependency manifest, test framework, or runtime product to drive live. The configured baseline command, scripts/check-docs.py, was re-confirmed passing on the target commit. There is no live-exercisable end-user surface beyond this check, so no further scenarios could be driven against a running product.
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
🔧 **Rebase** - 1 issue found → auto-fixed ✅
README.md- merge conflict rebasing onto origin/main🔧 Fix applied.
✅ Re-checked - no issues remain.
✅ **Review** - passed
✅ No issues found.
python3 scripts/check-docs.pypython3 scripts/check-docs.py (re-run on target commit 34b7369, exit 0, 10 markdown files, no problems found)✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.