检测环境间 schema 漂移

从 staging 和 production 导出 schema 并对比，使缺失索引或列在部署前被捕获。

使迁移安全

先测量问题。从 staging 和 production 导出 schema 并对比，使缺失索引或列在部署前被捕获。最常见的错误是未确认门禁能捕获你关心的问题就先加上。在接入 CI 之前，先对当前代码库运行 diff <(pg_dump –schema-only staging) <(pg_dump –schema-only prod) 并检查输出。

diff <(pg_dump --schema-only staging) <(pg_dump --schema-only prod)

验证与回滚

门禁就位后，让失败可操作。diff <(pg_dump –schema-only staging) <(pg_dump –schema-only prod) 失败时应指向具体文件和行号，而非泛泛的错误。在锁文件中固定工具版本，防止上游发布悄悄改变行为。每次拉取请求都应像审查测试结果一样审查门禁输出。

验证

在本地运行 diff <(pg_dump –schema-only staging) <(pg_dump –schema-only prod) 确认通过后推送。CI 中门禁应阻断不合规的拉取请求。若人为绕过门禁直接推送，应在下次定期扫描中被发现。

注意事项

The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
Configuration drift is possible if someone edits settings outside version control.