Native deployment status tracking in Forgejo: planned or external only?
Context Forgejo currently lacks a first-class deployment object with persistent status history. Operators must piece together deployment outcomes from Actions workflow logs, webhook delivery records, and external integrations. Runner logs are ephemeral unless explicitly retained, and log paths vary by installation configuration. Goal Determine whether the pr
forgejo