Skip to content

chore(release): map jake@nousresearch.com and simpolism@gmail.com to @simpolism - #25308

Closed
simpolism wants to merge 1 commit into
NousResearch:mainfrom
simpolism:chore/author-map-jake
Closed

chore(release): map jake@nousresearch.com and simpolism@gmail.com to @simpolism#25308
simpolism wants to merge 1 commit into
NousResearch:mainfrom
simpolism:chore/author-map-jake

Conversation

@simpolism

Copy link
Copy Markdown
Contributor

What does this PR do?

Map both addresses I commit from (simpolism@gmail.com for personal-account work, jake@nousresearch.com for work-account commits) to the existing GitHub account @simpolism in scripts/release.py's AUTHOR_MAP. Both addresses route to the same person; this prevents release notes from listing them as separate contributors and avoids each future PR carrying its own scripts/release.py noise.

Related Issue

None — this is housekeeping ahead of a small batch of feature/fix PRs from this account.

Type of Change

  • ♻️ Refactor (no behavior change)

(Strictly speaking this is metadata, not refactor — the change has no runtime effect at all. Closest checkbox.)

Changes Made

  • scripts/release.py: add two entries to AUTHOR_MAP:
    • "simpolism@gmail.com": "simpolism"
    • "jake@nousresearch.com": "simpolism"

How to Test

  1. Inspect the diff: git diff main -- scripts/release.py
  2. Confirm: only two lines added inside the AUTHOR_MAP dict, alphabetically near simon@simonmarcus.org
  3. No code changes, no behavior to verify at runtime

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits
  • I searched for existing PRs — no duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q — not run; metadata-only author-map change
  • I've added tests for my changes — N/A, metadata-only change
  • I've tested on my platform: Ubuntu 24.04

Documentation & Housekeeping

  • I've updated relevant documentation — N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — N/A
  • I've considered cross-platform impact — N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — N/A

…simpolism

Both addresses route to the same GitHub account (@simpolism / snav). Adding
the mappings here keeps release notes from showing two separate contributors
for what is one person's work, and unblocks subsequent PRs from this account
that would otherwise each need their own scripts/release.py noise.
@alt-glitch alt-glitch added type/refactor Code restructuring, no behavior change P3 Low — cosmetic, nice to have labels May 14, 2026
@teknium1

Copy link
Copy Markdown
Contributor

Salvaged via PR #25440 (#25440), merged to main as e905081. Your authorship is preserved on the cherry-picked commit.

Note: simpolism@gmail.com → simpolism already existed in AUTHOR_MAP on current main (line 47), so the new salvage PR adds only the jake@nousresearch.com entry next to it. Thanks for the cleanup!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low — cosmetic, nice to have type/refactor Code restructuring, no behavior change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants