Skip to content

gate: lower MAX_DEAD_TRI 140 -> 138 after #10500 removed two dead tri mentions (Closes #10513) #10514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gHashTag merged 1 commit into from
Oct 18, 2026
Merged

gate: lower MAX_DEAD_TRI 140 -> 138 after #10500 removed two dead tri mentions (Closes #10513) #10514

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tools/check_documented_commands_exist.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,7 @@ def scan_siblings(paths: list[Path], live_names: set[str]) -> tuple[list[tuple],
# is how a gate gets muted, and excluding those families by path would be an
# exclusion made by argument. So: the list prints every run, and the number can
# only fall. A new dead `tri` name still fails.
MAX_DEAD_TRI = 140
MAX_DEAD_TRI = 138

TRI_MUST_EXIST = ("now", "wave", "gen", "skill", "seal")
TRI_MUST_NOT_EXIST = ("gen-zig", "gen-dir", "spec", "git")
Expand Down
Loading