chore(links): repoint self-referential repo links to DIG-Network/digs (#764) - #28
Merged
Merged
Conversation
… (#764) The repo's remote already tracks DIG-Network/digs (the rename landed at the GitHub level), but README/SPEC/runbook prose, CI workflow comments, the issue-template links, action.yml's checkout target, and the Cargo.toml `repository` field on the three publishable crates (dig-client-wasm, digstore-core, digstore-subscription) still hard-coded the pre-rename DIG-Network/dig-store URL. Repoints all of them to DIG-Network/digs -- pure link/metadata edits, no crate/binary/CLI name change (dig-store/digstore/digs stay as-is). Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
Part of the F2d reference sweep (#764). The repo's git remote already tracks
DIG-Network/digs, but several hard-coded self-referential URLs still pointed at the pre-renameDIG-Network/dig-store:Cargo.tomlrepository = ...on the three publishable crates (dig-client-wasm,digstore-core,digstore-subscription)README.mdbadges/links,SPEC.md,runbooks/release.mdprose.github/ISSUE_TEMPLATE/config.yml(security policy / discussions links).github/workflows/nightly-release.ymlcommentaction.yml(uses:-style repository checkout target)Excluded (git-ignored
wasm-packbuild output, not source):crates/dig-client-wasm/pkg/**,crates/dig-client-wasm/pkg-node/**.Scope discipline: only the repo-URL/
repository=field changed; the crate/binary/CLI names (dig-store,digstore,digs) are untouched.Blast radius checked
Metadata/doc-only edits (Cargo.toml
repositoryfield, markdown, YAML comments/links). No code logic touched.Test plan
cargo build --workspaceclean (after the required guest-wasm build prereq)cargo fmt --all -- --checkclean0.17.0->0.17.1,dig-client-wasm0.1.0->0.1.1(patch -- link/metadata fix, no behavior change)Co-Authored-By: Claude noreply@anthropic.com