chore: replace legacy autogame-17 handles with EvoMap/evolver#413
Open
shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
Open
chore: replace legacy autogame-17 handles with EvoMap/evolver#413shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
shaun0927 wants to merge 1 commit intoEvoMap:mainfrom
Conversation
…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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Five locations in the repository still reference the legacy
personal-account handle
autogame-17:GitHub currently 301-redirects
autogame-17/capability-evolverandautogame-17/evolvertoEvoMap/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 orgslug where the issue tracker already lives.
Why this direction
EvoMap/evolveris where release publishing happens(
gh release listshows all three releases authored into this org).EvoMap/evolver(issues [Auto] Recurring failure: Repeated failures with gene: gene_gep_repair_from_errors #395 – docs(SKILL): network allow-list missing evomap.ai used by privacyClient, taskReceiver, and skillPublisher #411 are filed there).without requiring any behaviour change: the endpoints used at
runtime are identical after the redirect.
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_REPOliteralin
issueReporter.js. I can narrow the PR to just that line onrequest.
Testing
No runtime behaviour change. The module's HTTP targets resolve to
the same repository before and after the patch:
Scope
Five files, +5/−5 lines.
Closes #408.