2026-05-12 17:09:22 +00:00

name	description
codeberg-development-flow	Use when working in this repository on development flow, remotes, Codeberg or Forgejo CLI operations, commit signing, mirroring to GitHub, npm trusted publishing, release validation, or publishing @peezy.tech/codex-flows.

Codeberg Development Flow

Overview

Use Codeberg as the primary development forge and GitHub only as the npm trusted-publishing mirror.

Treat origin as Codeberg: git@codeberg.org:peezy-tech/codex-flows.git.
Treat github as the GitHub mirror: https://github.com/peezy-tech/codex-flows.git.
Push normal development to Codeberg first.
Push to GitHub only when the release workflow must publish to npm.
Do not add npm tokens to the repo or GitHub secrets. GitHub publishes through trusted publishing.
Use package name @peezy.tech/codex-flows, not @peezy-tech/codex-flows.

When asked to set up or verify the repo, check:

git remote -v
ssh -T git@codeberg.org
fj auth list
gpg --list-secret-keys --keyid-format=long

Expected local key files:

~/.ssh/id_ed25519_codeberg.pub
~/.config/codeberg-keys/matamune-codeberg-gpg.asc

Before release, run:

bun run --filter @peezy.tech/codex-flows release:check
bun run check:types
bun run test
git diff --check

Then:

Bump packages/codex-client/package.json.
Commit.
Push to Codeberg: git push origin main.
Push to GitHub mirror: git push github main.
Run GitHub workflow .github/workflows/publish-codex-flows.yml with confirm_package=@peezy.tech/codex-flows.
Verify npm dist-tag ls @peezy.tech/codex-flows.