hermes-agent/contributors
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-29 15:57:52 -05:00
..
emails chore: map contributor emails 2026-09-29 15:57:52 -05:00
README.md refactor(release): move the author map out of release.py 2026-09-24 14:08:22 -04:00
reattributed.tsv chore(attribution): re-attribute 0f4a98f87c to OutThisLife 2026-09-27 06:53:39 -05:00

Contributor email → GitHub login mappings

This directory replaces appending entries to AUTHOR_MAP in scripts/releases/authors_legacy.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/[email protected]:

janedoe
# PR #12345 salvage (gateway: fix session key routing)

Rules

  • Do NOT add new entries to AUTHOR_MAP in scripts/releases/authors_legacy.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.com and <login>@users.noreply.github.com) auto-resolve — no file needed.
  • The Contributor Attribution Check CI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.