Mads LorentzenandClaude Opus 5 07cec1f227 fix(ci): co-locate placeholder sentinels with the data they guard ...

cv/main_example.tex's sentinel was [YOUR_NAME] - a header comment and
the pdftitle, neither of which /setup's documented personalization
touches, so CI reported the file clean while it carried a real name,
address, phone and email (the review proved this end to end; the file
is the one CV the gitignore deliberately allows to be committed). The
guard now checks the \name{} and \email{} data lines, and 01's sentinel
moves from the <!-- SETUP comment onto [YOUR_EMAIL]. New test simulates
the /setup edit and requires every checked CV sentinel to be destroyed
by it. Review finding F28 (2026-08-19).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-19 20:47:51 +02:00

..

workflows

fix(ci): co-locate placeholder sentinels with the data they guard

2026-08-19 20:47:51 +02:00

FUNDING.yml

chore(funding): add GitHub Sponsors button alongside Ko-fi (#240)

2026-07-25 21:59:09 +02:00

PULL_REQUEST_TEMPLATE.md

docs: warn fork authors about GitHub's default PR base (#167)

2026-07-16 22:26:45 +02:00

upstream-wontport.txt

feat(upstream): add commit-level triage and weekly watch for forks (#305) (#320)

2026-08-11 19:11:24 +02:00