johba/disinto
1
0
Fork 0
Code Issues 5 Pull requests 1 Projects Releases Packages Wiki Activity Actions
disinto/supervisor/best-practices/forge.md
openhands a66bd91721 fix: Replace Codeberg dependency with local Forgejo instance (#611) 
- Add setup_forge() to bin/disinto: provisions Forgejo via Docker,
  creates admin + bot users (dev-bot, review-bot), generates API
  tokens, creates repo, and pushes code — all automated
- Rename env vars: CODEBERG_TOKEN→FORGE_TOKEN, REVIEW_BOT_TOKEN→
  FORGE_REVIEW_TOKEN, CODEBERG_REPO→FORGE_REPO, CODEBERG_API→
  FORGE_API, CODEBERG_WEB→FORGE_WEB, CODEBERG_BOT_USERNAMES→
  FORGE_BOT_USERNAMES (with backwards-compat fallbacks)
- Rename API helpers: codeberg_api()→forge_api(), codeberg_api_all()
  →forge_api_all() (with compat aliases)
- Add forge_url field to project TOML; load-project.sh derives
  FORGE_API/FORGE_WEB from forge_url + repo
- Update parse_repo_slug() to accept any host URL, not just codeberg
- Forgejo data stored under ~/.disinto/forgejo/ (not in factory repo)
- Update all 58 files: agent scripts, formulas, docs, site HTML

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-23 16:57:12 +00:00

1.8 KiB
Raw Blame History

Forge Best Practices

Rate Limiting

The forge (Forgejo/Gitea) may rate-limit SSH and HTTPS clones. Symptoms:

  • Woodpecker git step fails with exit code 128
  • Multiple pipelines fail in quick succession with the same error
  • Retriggers make it WORSE by adding more clone attempts

What To Do

  • Do NOT retrigger during a rate-limit storm. Wait 10-15 minutes.
  • Check if multiple pipelines failed on git step recently: 
    wpdb -c "SELECT number, status, to_timestamp(started) FROM pipelines WHERE repo_id=$WOODPECKER_REPO_ID AND status='failure' ORDER BY number DESC LIMIT 5;"
wpdb -c "SELECT s.name, s.exit_code FROM steps s JOIN pipelines p ON s.pipeline_id=p.id WHERE p.number=<N> AND p.repo_id=$WOODPECKER_REPO_ID AND s.state='failure';"
  • If multiple git failures with exit 128 in the last 15 min → it's rate limiting. Wait.
  • Only retrigger after 15+ minutes of no CI activity.

How To Retrigger Safely

cd <worktree> && git commit --allow-empty -m "ci: retrigger" --no-verify && git push origin <branch> --force

Prevention

  • The system runs 3 agents staggered by 3 minutes. During heavy development, many PRs trigger CI simultaneously.
  • One pipeline at a time is ideal on this VPS (resource + rate limit reasons).
  • If >3 pipelines are pending/running, do NOT create more work.

API Tokens

  • API token is in .env as FORGE_TOKEN — loaded via env.sh.
  • Review bot has a separate token ($FORGE_REVIEW_TOKEN) for formal reviews.
  • With local Forgejo, tokens don't expire. For remote forges, check provider docs.

Lessons Learned

  • Retrigger storm on 2026-03-12: supervisor + dev-agent both retriggered during rate limit, caused 5+ failed pipelines. Added cooldown awareness.
  • Empty commit retrigger works but adds noise to git history. Acceptable tradeoff.