brooktrails/changelog-action
Watch
2
0
Fork
You've already forked changelog-action
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(lib): explain the ambiguous-unicode warning this file triggers #3

Merged
rcsheets merged 1 commit from fix/unicode-note into main 2026-08-10 03:57:21 +00:00
Conversation 0 Commits 1 Files changed 1 +17
rcsheets commented 2026-08-10 03:57:12 +00:00
Owner
Copy link

Forgejo flags this file for ambiguous unicode. It is one line -- the sed
in normalize_summary, holding the curly quotes and em dash it folds to
ASCII -- and a scanner cannot tell a homoglyph hiding in code from a
character deliberately being matched, so the warning is a heuristic on
appearance rather than a finding.

Left unexplained, the next person to see it has to re-derive that, and
the obvious fix -- \uXXXX escapes -- is one GNU sed understands while
BusyBox and macOS sed do not, trading a cosmetic warning for a real
portability bug in a script whose premise is running anywhere with git,
curl, and jq. Better to record why it is there and that it should be
marked reviewed.

The comment names the characters by codepoint rather than repeating
them, so it does not add fresh instances of what is being flagged.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Forgejo flags this file for ambiguous unicode. It is one line -- the sed in normalize_summary, holding the curly quotes and em dash it folds to ASCII -- and a scanner cannot tell a homoglyph hiding in code from a character deliberately being matched, so the warning is a heuristic on appearance rather than a finding. Left unexplained, the next person to see it has to re-derive that, and the obvious fix -- \uXXXX escapes -- is one GNU sed understands while BusyBox and macOS sed do not, trading a cosmetic warning for a real portability bug in a script whose premise is running anywhere with git, curl, and jq. Better to record why it is there and that it should be marked reviewed. The comment names the characters by codepoint rather than repeating them, so it does not add fresh instances of what is being flagged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Forgejo flags this file for ambiguous unicode. It is one line -- the sed
in normalize_summary, holding the curly quotes and em dash it folds to
ASCII -- and a scanner cannot tell a homoglyph hiding in code from a
character deliberately being matched, so the warning is a heuristic on
appearance rather than a finding.

Left unexplained, the next person to see it has to re-derive that, and
the obvious fix -- \uXXXX escapes -- is one GNU sed understands while
BusyBox and macOS sed do not, trading a cosmetic warning for a real
portability bug in a script whose premise is running anywhere with git,
curl, and jq. Better to record why it is there and that it should be
marked reviewed.

The comment names the characters by codepoint rather than repeating
them, so it does not add fresh instances of what is being flagged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
rcsheets deleted branch fix/unicode-note 2026-08-10 03:57:21 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
brooktrails/changelog-action!3
No description provided.