Forgejo

Careful administration of a Forgejo (or Gitea) server over its /api/v1 REST API, authenticated with a scoped access token. Find-or-create organizations and repositories and converge their settings, run GitHub pull-mirrors (create via /repos/migrate, reconcile interval/visibility, queue immediate syncs), audit every mirror's sync health, drive pull requests (open, inspect with mergeability and head CI state, merge), and audit or repoint repository webhooks so a stale CI target is visible rather than silently undelivered. Mutations are find-or-create or reversible (archive/unarchive) apart from the guarded pr_merge; there are no delete methods — a failed migration's empty shell repo is detected and reported, never auto-deleted. Secrets are never emitted: mirror source credentials are write-only, and webhook operations neither read nor write the shared hook secret.