Skip to content

chore: replace legacy autogame-17 handles with EvoMap/evolver#413

Open
shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
shaun0927:chore/replace-legacy-autogame-17-handles
Open

chore: replace legacy autogame-17 handles with EvoMap/evolver#413
shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
shaun0927:chore/replace-legacy-autogame-17-handles

Conversation

@shaun0927
Copy link
Copy Markdown

Problem

Five locations in the repository still reference the legacy
personal-account handle autogame-17:

src/gep/issueReporter.js:14    DEFAULT_REPO = 'autogame-17/capability-evolver'
src/gep/skillPublisher.js:162  https://github.com/autogame-17/evolver
index.js:740                   https://github.com/autogame-17/evolver/issues
README.md:301                  | EVOLVER_ISSUE_REPO | autogame-17/capability-evolver | ... |
README.zh-CN.md:293            | EVOLVER_ISSUE_REPO | autogame-17/capability-evolver | ... |

GitHub currently 301-redirects autogame-17/capability-evolver and
autogame-17/evolver to EvoMap/evolver, so paths resolve today.
They depend on a GitHub redirect pinned to a personal-user account
(autogame-17).

See #408 for the full rationale.

Fix

Replace all five occurrences with EvoMap/evolver, the current org
slug where the issue tracker already lives.

Why this direction

If the project needs to keep the legacy name for some external
reason (e.g., existing indexers, older release URLs), the only entry
that materially matters for behaviour is the DEFAULT_REPO literal
in issueReporter.js. I can narrow the PR to just that line on
request.

Testing

No runtime behaviour change. The module's HTTP targets resolve to
the same repository before and after the patch:

$ node -e \"const r=require('./src/gep/issueReporter'); console.log(r)\"
{ maybeReportIssue: [Function: maybeReportIssue], ... }

$ node test/issueReporter.test.js
issueReporter.test.js: OK

Scope

Five files, +5/−5 lines.

Closes #408.

…oMap#408)

Five locations still reference the legacy personal-account handle
autogame-17. GitHub currently 301-redirects both
autogame-17/capability-evolver and autogame-17/evolver to
EvoMap/evolver, so paths work today, but they depend on a redirect
pinned to a personal-user account. If the autogame-17 account ever
deletes or transfers the old repository, the legacy name becomes
claimable and deployments with GITHUB_TOKEN set would start POSTing
auto-issue bodies elsewhere.

Replace:

  src/gep/issueReporter.js:14 DEFAULT_REPO literal
  src/gep/skillPublisher.js:162 Skill footer link
  index.js:740 error-message link
  README.md:301 EVOLVER_ISSUE_REPO default documentation
  README.zh-CN.md:293 ditto

All five now point directly at EvoMap/evolver, which is where the
issue tracker already lives.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: replace legacy autogame-17/capability-evolver references with EvoMap/evolver

1 participant