The forge cannot be read by strangers, and GitHub contributions cannot reach it #1073

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

Two halves of the same problem, both found while checking why nobody could see this repository.

1. The front door was locked. git.jayw.uk sits behind Cloudflare Access, and a wildcard
application covers *.jayw.uk. A stranger asking for the repository was redirected to a login page,
so the GitHub mirror was the de-facto front door — carrying 199 open pull requests and 788 open
issues
that no work on this side could see. Root on the host cannot fix this: Access is evaluated at
the edge, before the tunnel.

2. Contributions had no route in. Accounts here are closed by design (DISABLE_REGISTRATION = true, one account). That is the right posture, but it means a contributor's work needs a path that
does not involve them getting an account.

Acceptance:

  • The instance is publicly readable; Forgejo's own accounts remain the gate for every write.
  • One documented Access configuration, applied by a script rather than by hand, that accepts either a
    scoped token or the account Global API Key — and does not send one as the other.
  • scripts/gh-bridge.js carries issues and pull requests inward, preserving authorship, so CI runs
    here without the contributor having an account.
  • The bridge is idempotent: re-running it must not create a second copy of anything.
  • CONTRIBUTING.md tells a stranger which door to knock on.
Two halves of the same problem, both found while checking why nobody could see this repository. **1. The front door was locked.** `git.jayw.uk` sits behind Cloudflare Access, and a wildcard application covers `*.jayw.uk`. A stranger asking for the repository was redirected to a login page, so the GitHub mirror was the de-facto front door — carrying **199 open pull requests** and **788 open issues** that no work on this side could see. Root on the host cannot fix this: Access is evaluated at the edge, before the tunnel. **2. Contributions had no route in.** Accounts here are closed by design (`DISABLE_REGISTRATION = true`, one account). That is the right posture, but it means a contributor's work needs a path that does not involve them getting an account. Acceptance: - The instance is publicly readable; Forgejo's own accounts remain the gate for every write. - One documented Access configuration, applied by a script rather than by hand, that accepts either a scoped token or the account Global API Key — and does not send one as the other. - `scripts/gh-bridge.js` carries issues and pull requests inward, preserving authorship, so CI runs here without the contributor having an account. - The bridge is idempotent: re-running it must not create a second copy of anything. - CONTRIBUTING.md tells a stranger which door to knock on.
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#1073
No description provided.