4 Commits
Author SHA1 Message Date
James Elliott b3af55d156 docs: add license headers to remaining files (#13064) 2026-09-09 06:56:57 +00:00
Amir Zarrinkafsh 279ecb87de ci(lefthook): inline check tools with windows-safe quoting (#12149)
The tool-presence check was previously extracted to `check-tools.sh`
because lefthook on Windows wraps inline `run:` blocks in `sh.exe -c
"..."`, and any `"` in the inline body conflicts with the outer argv
wrap, truncating the script passed to `sh.exe`. The visible symptom was
a parser error like `unexpected EOF while looking for matching '"'`;
after dropping `MISSING=""` it became `unexpected end of file from 'if'
command` once enough of the script was clipped.

Inlines the check back into `.lefthook.yml` and rewrites the body to
contain zero `"` characters. Bare-word variables (`${TOOL}`, `${COUNT}`,
`${MISSING}`) are left unquoted: tool names are hard-coded bare words,
`${COUNT}` is numeric, and the unquoted `${MISSING}` expansions inside
`echo`/`sed` rejoin word splits with single spaces, producing the same
final string. Literal space-bearing parts switch to single-quoted
strings (`' and '`, `'❌ You must install '`), which are inert under the
Windows wrap because the CRT argv parser only toggles on `"`. The
standalone `check-tools.sh` script is removed.

Verified via `lefthook validate` and `/bin/sh -c "..."` for all four
formatter branches (1, 2, 3, 4 missing tools); output matches the
original Oxford-style message. Windows confirmed; the earlier
`unexpected end of file from 'if'` error no longer reproduces.

Refs #12142

Signed-off-by: Amir Zarrinkafsh <3339418+nightah@users.noreply.github.com>
2026-05-24 01:43:42 +00:00
Brynn CrowleyandRicardo Rivera 24b1f29cec ci(build): use lf line endings for windows compatability (#12142)
Improves unofficial support for developing on windows.

Closes #12080, Closes #12081

---------

Signed-off-by: Brynn Crowley <littlehill723@gmail.com>
Co-authored-by: Ricardo Rivera <rrivera@solutionspr.net>
2026-05-23 03:46:52 +00:00
James Elliott 319a8cf9d4 fix(notification): text emails not encoded properly (#3854)
This fixes an issue where the plain text portion of emails is not encoded with quoted printable encoding.
2022-08-27 07:39:20 +10:00