4d79bd3d02
Two hardening guards extracted from #82766 by @StanleyStetson: - bool is an int subclass, so a JSON `true` in truncate_before_user_ordinal coerced via int() to ordinal 1 and aimed a CONFIRMED rewind at the second user turn — the same silent-loss class as #82756. Reject with 4004. - confirm_truncate with no truncation target is leaked client rewind state on an ordinary submit; fail fast with 4004 instead of silently ignoring the flag, so the corrupted client state is surfaced. Part of the composite fix for #82756. |
||
|---|---|---|
| .. | ||
| emails | ||
| README.md | ||
README.md
Contributor email → GitHub login mappings
This directory replaces appending entries to AUTHOR_MAP in
scripts/release.py. The old dict caused constant merge conflicts when
several salvage PRs landed at once — every PR edited the same lines of the
same file. Here, each mapping is its own file, and file additions never
conflict.
Adding a mapping
One file per commit-author email, under emails/:
python3 scripts/add_contributor.py <email> <github-login>
# or by hand:
echo "<github-login>" > contributors/emails/<email>
- File name = the exact commit-author email (as shown by
git log --format='%ae'). - File content = the GitHub login on the first non-comment line.
Lines starting with
#are comments (use them for the PR reference).
Example — contributors/emails/jane.doe@example.com:
janedoe
# PR #12345 salvage (gateway: fix session key routing)
Rules
- Do NOT add new entries to
AUTHOR_MAPinscripts/release.py. That dict is frozen legacy data; the release tooling merges it with this directory (directory entries win on duplicates). - GitHub noreply emails (
<id>+<login>@users.noreply.github.comand<login>@users.noreply.github.com) auto-resolve — no file needed. - The
Contributor Attribution CheckCI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.