-
-
Notifications
You must be signed in to change notification settings - Fork 0
fix(ci): the invisible-character gate never matched anything #67
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
bc5d4d2
1e862cb
91c744a
5972afa
68b2de4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -121,7 +121,7 @@ jobs: | |
| # Checks for: zero-width spaces, zero-width joiners, BOM, soft hyphens, | ||
| # non-breaking spaces, null bytes, and other invisible Unicode in source files. | ||
| set +e | ||
| PATTERNS='\xc2\xa0|\xe2\x80\x8b|\xe2\x80\x8c|\xe2\x80\x8d|\xef\xbb\xbf|\xc2\xad|\xe2\x80\x8e|\xe2\x80\x8f|\xe2\x80\xaa|\xe2\x80\xab|\xe2\x80\xac|\xe2\x80\xad|\xe2\x80\xae|\x00' | ||
| PATTERNS='(*UTF)[\x00-\x08\x0B\x0C\x0E-\x1F\x{a0}\x{ad}\x{200b}-\x{200f}\x{202a}-\x{202f}\x{2060}\x{2066}-\x{2069}\x{feff}]' | ||
| find "$GITHUB_WORKSPACE" \ | ||
| -not -path '*/.git/*' -not -path '*/node_modules/*' \ | ||
| -not -path '*/.deno/*' -not -path '*/target/*' \ | ||
|
|
@@ -132,7 +132,7 @@ jobs: | |
| -o -name '*.yml' -o -name '*.yaml' -o -name '*.md' -o -name '*.adoc' \ | ||
| -o -name '*.idr' -o -name '*.zig' -o -name '*.v' -o -name '*.jl' \ | ||
| -o -name '*.gleam' -o -name '*.hs' -o -name '*.ml' -o -name '*.sh' \) \ | ||
| -exec grep -Prl "$PATTERNS" {} \; > /tmp/empty-lint-results.txt 2>/dev/null | ||
| -exec grep -aPrl "$PATTERNS" {} \; > /tmp/empty-lint-results.txt 2>/dev/null | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ⚪ LOW RISK Suggestion: The recursive flag is unnecessary when targeting individual files, and the current command spawns a new process per file. Performance can be improved by batching files and removing the error suppression. Try running the following prompt in your coding agent:
|
||
| EL_EXIT=$? | ||
| set -e | ||
|
|
||
|
|
@@ -141,13 +141,41 @@ jobs: | |
| echo "exit_code=$EL_EXIT" >> "$GITHUB_OUTPUT" | ||
| echo "ready=true" >> "$GITHUB_OUTPUT" | ||
|
|
||
| # Blocking subset: C0 controls and NUL only (owner ruling 2026-08-28). | ||
| # Invisible Unicode (NBSP/BOM/zero-width) stays ADVISORY - about 2,100 | ||
| # estate files carry it as legitimate typography in prose. | ||
| blocking=0 | ||
| while IFS= read -r bf; do | ||
| [ -z "$bf" ] && continue | ||
| if grep -qaP '\x00|[\x01-\x08\x0B\x0C\x0E-\x1F]' "$bf"; then | ||
| blocking=$((blocking+1)) | ||
| echo "::error file=${bf#$GITHUB_WORKSPACE/}::C0 control characters or NUL bytes - file corruption, blocks the gate" | ||
| fi | ||
| done < /tmp/empty-lint-results.txt | ||
| echo "blocking=$blocking" >> "$GITHUB_OUTPUT" | ||
|
|
||
| # Emit annotations for each file with invisible chars | ||
| while IFS= read -r filepath; do | ||
| [ -z "$filepath" ] && continue | ||
| REL_PATH="${filepath#$GITHUB_WORKSPACE/}" | ||
| echo "::warning file=${REL_PATH}::Invisible Unicode characters detected (zero-width space, BOM, NBSP, etc.)" | ||
| done < /tmp/empty-lint-results.txt | ||
|
|
||
| # Enforce (owner ruling 2026-08-28): C0/NUL corruption BLOCKS; other | ||
| # invisible Unicode stays advisory. Enforcement lives inside this step | ||
| # so a crash above fails the job directly - counts can never arrive | ||
| # empty into a separate check that then passes silently. | ||
| if [ "$EL_EXIT" -ne 0 ]; then | ||
| echo "::warning::invisible-character scan exited $EL_EXIT - results may be incomplete" | ||
| fi | ||
| if [ "${blocking:-0}" -gt 0 ]; then | ||
| echo "## Empty-linter: BLOCKED - $blocking file(s) with C0/NUL corruption" >> "$GITHUB_STEP_SUMMARY" | ||
| echo "::error::$blocking file(s) contain C0 control characters or NUL bytes - corruption, not typography. See file annotations." | ||
| exit 1 | ||
| elif [ "${FINDINGS:-0}" -gt 0 ]; then | ||
| echo "::notice::$FINDINGS file(s) carry invisible Unicode (NBSP/BOM/zero-width) - advisory only" | ||
| fi | ||
|
|
||
| - name: Write summary | ||
| run: | | ||
| if [ "${{ steps.lint.outputs.ready }}" = "true" ]; then | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Add the separate leading-BOM check.
PATTERNSincludes\x{feff}, but it does not detect a UTF-8 BOM at the start of a file. A BOM-only file is therefore absent from/tmp/empty-lint-results.txt, so later reporting does not see it. Inspect the first three bytes (EF BB BF) separately, merge the path before classification, and de-duplicate it. Keep this pattern for mid-file BOMs.The PR objective requires a separate leading-BOM check.
🤖 Prompt for AI Agents