The confusion
There are two distinct repos with confusingly-related names, and a local clone whose
directory name points at the wrong one:
|
repo |
what it is |
| this repo |
bounded-systems/site |
the static site (copy gate via the vendored string-audit submodule; PRs #30/#31) |
| separate |
bounded-systems/bounded.tools |
a different project — a prx GitHub App receiver / "Front Desk" stub |
The trap: a local checkout of site lives in a directory literally named
…/bounded-systems/bounded.tools/ — its git remote get-url origin is
https://github.com/bounded-systems/site.git, not bounded.tools.
$ git -C …/bounded-systems/bounded.tools remote get-url origin
https://github.com/bounded-systems/site.git
So bounded.tools/ (the dir) ≠ bounded.tools (the repo). Querying by the dir name
(gh api repos/bounded-systems/bounded.tools/...) hits the other repo, which has no
vendor/string-audit submodule — making it look like the copy gate had vanished, when
really you're looking at the wrong repo.
Why it matters
Anyone (human or agent) navigating from the local directory name to the GitHub repo lands
on the wrong project. It cost real time to untangle while bumping the string-audit copy
gate.
Suggested fix (pick one)
- Rename the local clone dir to
site/ so dir name == repo name (cleanest), or
- add a short note in
site's README clarifying site vs bounded.tools and that the
canonical clone path is …/bounded-systems/site, or
- if
bounded.tools was renamed to site upstream, re-clone so stale local dirs don't
linger under the old name.
Filed at the request of a maintainer after the naming cost time during the string-audit
v0.4.0 copy-gate bump (#31).
The confusion
There are two distinct repos with confusingly-related names, and a local clone whose
directory name points at the wrong one:
bounded-systems/sitestring-auditsubmodule; PRs #30/#31)bounded-systems/bounded.toolsThe trap: a local checkout of
sitelives in a directory literally named…/bounded-systems/bounded.tools/— itsgit remote get-url originishttps://github.com/bounded-systems/site.git, notbounded.tools.So
bounded.tools/(the dir) ≠bounded.tools(the repo). Querying by the dir name(
gh api repos/bounded-systems/bounded.tools/...) hits the other repo, which has novendor/string-auditsubmodule — making it look like the copy gate had vanished, whenreally you're looking at the wrong repo.
Why it matters
Anyone (human or agent) navigating from the local directory name to the GitHub repo lands
on the wrong project. It cost real time to untangle while bumping the
string-auditcopygate.
Suggested fix (pick one)
site/so dir name == repo name (cleanest), orsite's README clarifyingsitevsbounded.toolsand that thecanonical clone path is
…/bounded-systems/site, orbounded.toolswas renamed tositeupstream, re-clone so stale local dirs don'tlinger under the old name.
Filed at the request of a maintainer after the naming cost time during the string-audit
v0.4.0 copy-gate bump (#31).