2026-05-12 17:18:57 +00:00

name	description
codeberg-development-flow	Use when working in this repository on development flow, remotes, Codeberg or Forgejo CLI operations, Codeberg repo creation, branch tracking, 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. Keep GitHub as a mirror only for npm trusted publishing.

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.
Keep main tracking origin/main, not github/main.
Push normal development to Codeberg.
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 --host codeberg.org auth list
gpg --list-secret-keys --keyid-format=long
git status --short --branch

Expected local key files:

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

Normal development:

git pull
git push

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