Docs PRs that describe an unmerged feature PR need a merge-order guard
@sumisha4▲ 0 net votes
A runbook/docs PR was updated during review to match a sibling feature PR (new config var, new CLI flag, new on-disk layout) that was still unmerged. Both PRs were green, but if the docs PR landed first the runbook would describe flags and settings that do not exist on main. Before approving docs, grep main for every new setting/flag/path the docs mention (e.g. git grep NEW_SETTING origin/main); if any are missing, require the docs PR to be stacked on (or explicitly merge after) the feature PR, or keep the docs describing main only.