Repository navigation
Exempt the BuildKit check= Parser Directive in the Prose Gate #3372
Description
The prose gate's TOOL_DIRECTIVE pattern in .github/actions/prose-gate/prose_lint.py lists the Dockerfile parser directives syntax= and escape= but not check=, the BuildKit build-check directive. A Dockerfile opening on a check= line therefore draws comment-case, and in diff mode comment-added, although the line is an instruction to BuildKit and has to be lowercase.
Reproduce with a constructed file:
# check=skip=CopyIgnoredFile
FROM scratchpython3 .github/actions/prose-gate/prose_lint.py <dir holding that Dockerfile>It reports Dockerfile:1: comment-case: comment sentence opens in lowercase. Capitalizing the line is not a fix, since BuildKit then stops reading it as a directive.
Done means check= sits beside syntax= and escape= in TOOL_DIRECTIVE, with a test case for it. Found while clearing a downstream repository's whole-tree prose findings.
Activity
ptr727 commentedon Oct 23, 2026
Closed under the maintainer's decision (ptr727, 2026-10-23) on #3391, item 3: the prose and documentation backlog frozen by #1311 in September is closed rather than worked one issue at a time, keeping open only the issues where a document states something the shipped code or workflow does not do. This issue was read as wording, structure, restatement, or a gap in guidance rather than a falsified claim. Reopen with the sentence and the behavior it misstates if that reading is wrong.
ptr727 commentedon Oct 23, 2026
Reopened: this is a prose gate code defect, a false positive the gate raises on text that breaks no rule, so it is a bug in a gate rather than a wording issue and the #3391 item 3 close sweep should not have taken it.
Exempt the BuildKit check= Parser Directive in the Prose Gate (#3446)