Teknium
b907b7eb85
- Widen the permanent-rejection match to the exact relay phrasings seen in production (#97502): 'not a channel member' and 'auth-required', alongside 'restricted'. - Close the re-adoption hole called out in review: _discover_dms() (both the dms-list path and the channels-list fallback) now skips channels in _restricted_channels, so a restricted channel dropped at runtime cannot be silently re-added by the next discovery sweep and re-trigger the rejection. - Credit: runtime CLOSED matching terms from PR #97502 by @repfigit; the per-subscription drop + restricted set is PR #76850 by @xozai.
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.