deploy: upstream repo 0xWheatyz/api-company does not exist — deployment PR blocked #41
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deployment Cycle — 2026-05-26
The ship cycle attempted to open a deployment PR from
leeworks-agents/api-company:main→0xWheatyz/api-company:mainbut the upstream canonical repo does not yet exist on Gitea.Fork status
c899450(9 commits of work ready to ship)Cannot find repository: 0xWheatyz/api-companyAction required
Please create the upstream repo
0xWheatyz/api-companyon Gitea so the agent can open the deployment PR in the next ship cycle.Accumulated work ready to deploy
2026-05-26 ship cycle: Upstream repo
0xWheatyz/api-companystill does not exist on Gitea. Forkleeworks-agents/api-companyis fully up-to-date (latest:01bfe26— docs/secrets-checklist.md).kustomize build flux/passes cleanly. Deployment PR cannot be created until a human creates0xWheatyz/api-companyand grants push access. Please create the upstream repo to unblock the deployment pipeline (see also #47).Status 2026-05-26 — Still blocked on upstream repo creation. No change since last cycle. See #47 for the manual operator action required. All fork work continues to accumulate and is ready to ship.
2026-05-27 triage cycle — Still blocked on
0xWheatyz/api-companynot existing (see #47). Fork main is at commitb371c39(55 merged PRs, all agent work staged). No new work to do until the upstream repo is created.Triage cycle 2026-05-27 — Still blocked on
0xWheatyz/api-companynot existing (see #47). No new work possible until the operator creates the upstream repo.Superseded by #47 which is the canonical operator-action issue for creating 0xWheatyz/api-company. Closing this ship-cycle error report to reduce backlog noise; tracking continues in #47.