Repository navigation
chore: point repo references at the graphprotocol org - #677
Merged
Merged
Conversation
totalreclaw, totalreclaw-internal and totalreclaw-relay moved from p-diogo to graphprotocol. Update links, package/crate/subgraph manifest repository fields, the deploy-app dispatch target and the QA bug-report default repo to the new org. package.json repository.url must match the publishing repo for `npm publish --provenance`, so the next npm release from graphprotocol/totalreclaw would have been rejected without this. The QA bug-report public-repo denylists (Python + plugin) keep the p-diogo/* slugs alongside the new graphprotocol ones, since GitHub redirects the old slugs to the public repo; a test pins that. Left untouched: CHANGELOG files (historical record), the totalreclaw-hermes/-website/-plugin repos (not moved), the npm publisher account name, and The Graph Explorer subgraph URL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
🔗 Vault SPA preview: https://7868b40b.totalreclaw-app.pages.dev Backed by staging relay ( |
p-diogo
added a commit
to p-diogo/totalreclaw-hermes
that referenced
this pull request
Oct 19, 2026
totalreclaw and totalreclaw-internal moved from p-diogo to graphprotocol. Links still redirect; this updates them to the canonical location. Counterpart of graphprotocol/totalreclaw#677. Co-authored-by: Pedro Diogo <pdiogo@dashboards-tgf.tail8fab30.ts.net> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2 of 3 tasks
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
1 participant
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.
What
totalreclaw,totalreclaw-internalandtotalreclaw-relaymoved fromp-diogotographprotocol. This updates the 64 non-changelog files that still pointed at the old org.Why it matters beyond links
npm publish --provenancerejects a publish whosepackage.jsonrepository.urldoesn't match the repo the workflow runs in.client/,mcp/andskill/plugin/all saidp-diogo/totalreclaw, so the next npm release would have failed.deploy-app.ymlnow dispatches tographprotocol/totalreclaw-internal.qa_bug_report.py/qa-bug-report.tsis nowgraphprotocol/totalreclaw-internal. Both public-repo denylists keep thep-diogo/*slugs alongside the newgraphprotocol/*ones, because the old slugs redirect to the public repo. A new test in each client pins that.repositoryfields:Cargo.toml(core + memory),skill.json, subgraph YAMLs (metadata only; this changes the manifest hash on the next deploy, nothing else).SKILL.md, the issue-template contact links, the README CI badge, guides, andCLAUDE.md.Deliberately unchanged
CHANGELOG*.md: historical record; old links redirect.p-diogo/totalreclaw-hermes/-website/-plugin: not moved.p-diogo, which is the npm publisher account name.thegraph.com/explorer/subgraph/p-diogo/totalreclaw: Graph Explorer, not GitHub.Testing
2524 passed, 13 skipped, 1 xfailed.qa-bug-report75/75,config28/28,embedder-network16/16,embedding-fallback-tag9/9). The full suite is left to CI.tsc --noEmiterrors already exist, and none are in changed files (builduses--noCheck).npm run buildpasses.Not covered by this PR (settings outside the repo)
p-diogo/totalreclaw.INTERNAL_DISPATCH_PAT,PUBLIC_ISSUE_PAT) are scoped to the old user-owned repos. They likely need re-issuing withgraphprotocolas resource owner.🤖 Generated with Claude Code