Cross-branch ID consistency
When a project uses canonical ID tables (analytics website IDs, API token tags, external service identifiers), files in different folders/branches must reference IDs that match the canonical table - not hardcoded copies that drift.
When it fires#
Scans files matching applies-to.files for ID patterns declared in
website-ids.toml. Flags any hardcoded ID that doesn’t match the canonical
table’s entry for the file’s location (folder → domain → expected ID).
Override#
If a file deliberately uses a different ID (e.g., dev vs prod environments):
add <!-- appframes:disable documentation/cross-branch-id-consistency --> at
the top.
WARN lets the push through and records the finding. Turn frames on per repo on the dashboard's Policy page - see choosing what the gate checks.
Source on GitHub Live demo How it works Questions: contact@nimblegate.com