Skip to content

Confusing: site is cloned locally as bounded.tools/, and a separate bounded-systems/bounded.tools repo exists #32

Description

@bdelanghe

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions