Every project URL still points at GitHub, which is not where development happens #1061

Closed
opened 2026-11-08 14:06:03 +00:00 by jaylouisw · 0 comments
Owner

The project moved to Forgejo and the links did not follow.

The README tells people to clone from GitHub, the hardware-request button opens a GitHub issue form,
SECURITY.md sends vulnerability reports to a GitHub advisory page, package.json advertises a GitHub
repository, and the generated wiki links to GitHub throughout. None of those is where development
happens, so the first instruction a contributor follows takes them somewhere else - and nothing
failed when that happened, because a stale URL looks like every other string in the repository.

Found while checking: the GitHub repository is live, un-archived and current, with 30 open pull
requests
and 988 open issues. Those PRs run CI there (the workflows are gated to run on
GitHub), go green, and are invisible here.

Acceptance:

  • One definition of where the project lives (scripts/canonical.js), used by the scripts.
  • A build-failing check that no tracked file points at the old location, that the README clone URL
    and CI badge match the canonical base, and that no instruction depends on the GitHub CLI.
  • The triage scripts stop calling gh - which on this machine is installed and authenticated, so it
    would silently answer about the GitHub mirror and report a backlog nobody is working on.
  • A missing tracker token reports "cannot look" and exits non-zero, never "no open requests".
  • docs/MIRRORING.md states what syncs (git, one way), what cannot (PRs, issues), and the rule that
    keeps the two from fighting.

Not in scope: the Cloudflare Access gate on the canonical host, and the PR bridge itself. Both are
tracked separately because they need credentials and a job, not a URL edit.

The project moved to Forgejo and the links did not follow. The README tells people to clone from GitHub, the hardware-request button opens a GitHub issue form, SECURITY.md sends vulnerability reports to a GitHub advisory page, package.json advertises a GitHub repository, and the generated wiki links to GitHub throughout. None of those is where development happens, so the first instruction a contributor follows takes them somewhere else - and nothing failed when that happened, because a stale URL looks like every other string in the repository. Found while checking: the GitHub repository is live, un-archived and current, with **30 open pull requests** and **988 open issues**. Those PRs run CI there (the workflows are gated to run on GitHub), go green, and are invisible here. Acceptance: - One definition of where the project lives (`scripts/canonical.js`), used by the scripts. - A build-failing check that no tracked file points at the old location, that the README clone URL and CI badge match the canonical base, and that no instruction depends on the GitHub CLI. - The triage scripts stop calling `gh` - which on this machine is installed and authenticated, so it would silently answer about the GitHub mirror and report a backlog nobody is working on. - A missing tracker token reports "cannot look" and exits non-zero, never "no open requests". - `docs/MIRRORING.md` states what syncs (git, one way), what cannot (PRs, issues), and the rule that keeps the two from fighting. Not in scope: the Cloudflare Access gate on the canonical host, and the PR bridge itself. Both are tracked separately because they need credentials and a job, not a URL edit.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#1061
No description provided.