chore: make Forgejo the source of authority, GitHub a read-only mirror #1

Closed
opened 2026-10-27 14:50:54 +00:00 by crapougnax · 0 comments
Owner

Context

git.qtrn.io/Quatrain/Core already receives every push and mirrors it to GitHub (push mirror, sync on commit). Issues, pull requests and npm publishing still live on GitHub, and publishing has been broken since GitHub Actions were decommissioned (55575bc): develop has no publish job.

Goal

Forgejo becomes the single source of authority. GitHub stays a read-only mirror.

Scope

  • .forgejo/workflows/publish.yaml: beta on develop, latest on main, secret NPM_TOKEN, version bumps committed back with [skip ci].
  • bin/publish_all.js: no --provenance outside GitHub Actions (Forgejo sets GITHUB_ACTIONS=true for compatibility); GitHub Packages publishing only when running on GitHub.
  • repository / bugs / homepage of every package point to git.qtrn.io/Quatrain/Core.
  • README banner, CONTRIBUTING.md, GEMINI.md, guidelines/*: contribution flow on Forgejo (API instead of gh).
  • Open GitHub issues recreated here with a backlink, then closed on GitHub with a pointer.
  • Open GitHub PR #70 recreated here.
  • GitHub: issues, wiki and projects disabled; description "Read-only mirror"; ruleset restricting direct pushes to the mirror account.

Acceptance criteria

  • A merge into develop publishes changed packages with the beta tag from Forgejo Actions.
  • No open issue or PR remains on GitHub; GitHub rejects issues and non-mirror pushes.
## Context `git.qtrn.io/Quatrain/Core` already receives every push and mirrors it to GitHub (push mirror, sync on commit). Issues, pull requests and npm publishing still live on GitHub, and publishing has been broken since GitHub Actions were decommissioned (`55575bc`): develop has no publish job. ## Goal Forgejo becomes the single source of authority. GitHub stays a read-only mirror. ## Scope - [ ] `.forgejo/workflows/publish.yaml`: beta on `develop`, latest on `main`, secret `NPM_TOKEN`, version bumps committed back with `[skip ci]`. - [ ] `bin/publish_all.js`: no `--provenance` outside GitHub Actions (Forgejo sets `GITHUB_ACTIONS=true` for compatibility); GitHub Packages publishing only when running on GitHub. - [ ] `repository` / `bugs` / `homepage` of every package point to `git.qtrn.io/Quatrain/Core`. - [ ] README banner, `CONTRIBUTING.md`, `GEMINI.md`, `guidelines/*`: contribution flow on Forgejo (API instead of `gh`). - [ ] Open GitHub issues recreated here with a backlink, then closed on GitHub with a pointer. - [ ] Open GitHub PR #70 recreated here. - [ ] GitHub: issues, wiki and projects disabled; description "Read-only mirror"; ruleset restricting direct pushes to the mirror account. ## Acceptance criteria - A merge into `develop` publishes changed packages with the `beta` tag from Forgejo Actions. - No open issue or PR remains on GitHub; GitHub rejects issues and non-mirror pushes.
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
quatrain/core#1
No description provided.