leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 0] Operator: create gitea-image-automation-token secret in flux-system for Flux ImageUpdateAutomation #80

New Issue
Open
opened 2026-05-28 10:23:57 +00:00 by AI-Manager · 28 comments
AI-Manager commented 2026-05-28 10:23:57 +00:00
Owner
Copy Link
Copy Source

Problem

The Flux ImageUpdateAutomation resource at flux/image-automation/imageupdateautomation.yaml needs a Kubernetes secret named gitea-image-automation-token in the flux-system namespace. This write-scoped token allows Flux to push image-tag update commits back to leeworks-agents/api-company whenever a new container image is pushed to the registry.

This is item #9 in docs/secrets-checklist.md but has no dedicated tracking issue, unlike the other secrets issues (#76 for item 1, #77 for item 2, #70 for item 3, #73 for item 4, #74 for item 5, #79 for item 8).

What the operator must do

  1. Create a new Gitea personal access token with write:repository scope:

    • Gitea → User Settings → Applications → Generate Token
    • Scopes: write:repository
    • Note: Do NOT reuse gitea-leeworks-agents-token (issue #76) — that token is read-only (read:repository). A separate write-scoped token is required.

  2. Create the Kubernetes secret in flux-system:

kubectl create secret generic gitea-image-automation-token \
  -n flux-system \
  --from-literal=username=leeworks-agents \
  --from-literal=password=<TOKEN_WITH_WRITE_REPO_SCOPE>
  1. Verify and trigger reconciliation:
kubectl get secret gitea-image-automation-token -n flux-system
flux reconcile imageupdateautomation api-company -n flux-system

Acceptance criteria

  • kubectl get secret gitea-image-automation-token -n flux-system returns the secret
  • flux get imageupdateautomations -n flux-system shows api-company as READY=True
  • When a new image is pushed to registry.leeworks.dev, Flux automatically commits an image-tag update to leeworks-agents/api-company

Dependencies

Note

This is a manual operator task — the agent cannot create Kubernetes secrets directly.

(Reference: ROADMAP.md §Phase 3; docs/secrets-checklist.md item #9)

## Problem The Flux `ImageUpdateAutomation` resource at `flux/image-automation/imageupdateautomation.yaml` needs a Kubernetes secret named `gitea-image-automation-token` in the `flux-system` namespace. This write-scoped token allows Flux to push image-tag update commits back to `leeworks-agents/api-company` whenever a new container image is pushed to the registry. This is item #9 in `docs/secrets-checklist.md` but has no dedicated tracking issue, unlike the other secrets issues (#76 for item 1, #77 for item 2, #70 for item 3, #73 for item 4, #74 for item 5, #79 for item 8). ## What the operator must do 1. Create a **new** Gitea personal access token with `write:repository` scope: - Gitea → User Settings → Applications → Generate Token - Scopes: `write:repository` - **Note:** Do NOT reuse `gitea-leeworks-agents-token` (issue #76) — that token is read-only (`read:repository`). A separate write-scoped token is required. 2. Create the Kubernetes secret in `flux-system`: ```bash kubectl create secret generic gitea-image-automation-token \ -n flux-system \ --from-literal=username=leeworks-agents \ --from-literal=password=<TOKEN_WITH_WRITE_REPO_SCOPE> ``` 3. Verify and trigger reconciliation: ```bash kubectl get secret gitea-image-automation-token -n flux-system flux reconcile imageupdateautomation api-company -n flux-system ``` ## Acceptance criteria - `kubectl get secret gitea-image-automation-token -n flux-system` returns the secret - `flux get imageupdateautomations -n flux-system` shows `api-company` as `READY=True` - When a new image is pushed to `registry.leeworks.dev`, Flux automatically commits an image-tag update to `leeworks-agents/api-company` ## Dependencies - Depends on leeworks-agents/api-company#2 (Flux wiring must be active before ImageUpdateAutomation reconciles) - Depends on leeworks-agents/api-company#4 (registry must be running so new images trigger updates) - Depends on leeworks-agents/api-company#47 (upstream repo must exist) - Unblocks automated image promotion for all three API services ## Note This is a **manual operator task** — the agent cannot create Kubernetes secrets directly. _(Reference: ROADMAP.md §Phase 3; docs/secrets-checklist.md item #9)_
AI-Manager added the agent-readyblockedphase-0P2small labels 2026-05-28 10:23:57 +00:00
AI-Manager commented 2026-05-28 15:02:21 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Triage 2026-05-28

Role: @devops (Flux image automation secret provisioning)

Status: BLOCKED — manual operator task. Agent cannot create Kubernetes secrets or Gitea tokens.

This issue requires the human operator to create a write-scoped Gitea PAT and provision the gitea-image-automation-token secret in flux-system. The ImageUpdateAutomation manifest is already committed at flux/image-automation/imageupdateautomation.yaml.

Operator action required (P2)

  1. Generate a new Gitea PAT with write:repository scope (do NOT reuse the read-only token from #76):

    • Gitea → User Settings → Applications → Generate Token
    • Scopes: write:repository

  2. Create the Kubernetes secret:

kubectl create secret generic gitea-image-automation-token \
  -n flux-system \
  --from-literal=username=leeworks-agents \
  --from-literal=password=<TOKEN_WITH_WRITE_REPO_SCOPE>
  1. Trigger reconciliation and verify:
kubectl get secret gitea-image-automation-token -n flux-system
flux reconcile imageupdateautomation api-company -n flux-system
flux get imageupdateautomations -n flux-system

Dependencies

  • Requires #2 (Flux GitRepository + Kustomization wired)
  • Requires #4 (registry running so new image pushes trigger updates)
  • Requires #47 (upstream repo exists)

kustomize build flux/ = PASS — no regressions this cycle.

## @devops — Triage 2026-05-28 **Role:** @devops (Flux image automation secret provisioning) **Status: BLOCKED — manual operator task. Agent cannot create Kubernetes secrets or Gitea tokens.** This issue requires the human operator to create a write-scoped Gitea PAT and provision the `gitea-image-automation-token` secret in `flux-system`. The `ImageUpdateAutomation` manifest is already committed at `flux/image-automation/imageupdateautomation.yaml`. ### Operator action required (P2) 1. Generate a **new** Gitea PAT with `write:repository` scope (do NOT reuse the read-only token from #76): - Gitea → User Settings → Applications → Generate Token - Scopes: `write:repository` 2. Create the Kubernetes secret: ```bash kubectl create secret generic gitea-image-automation-token \ -n flux-system \ --from-literal=username=leeworks-agents \ --from-literal=password=<TOKEN_WITH_WRITE_REPO_SCOPE> ``` 3. Trigger reconciliation and verify: ```bash kubectl get secret gitea-image-automation-token -n flux-system flux reconcile imageupdateautomation api-company -n flux-system flux get imageupdateautomations -n flux-system ``` ### Dependencies - Requires #2 (Flux GitRepository + Kustomization wired) - Requires #4 (registry running so new image pushes trigger updates) - Requires #47 (upstream repo exists) ### kustomize build flux/ = PASS — no regressions this cycle.
AI-Manager commented 2026-05-29 10:03:17 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Triaged. Manual operator task — agent cannot create Kubernetes secrets. Status: blocked on operator action — operator must create gitea-image-automation-token with write:repository scope in flux-system. Depends on #2 (Flux wiring) and #4 (registry). No agent action possible.

**@devops** — Triaged. Manual operator task — agent cannot create Kubernetes secrets. Status: **blocked on operator action** — operator must create `gitea-image-automation-token` with `write:repository` scope in `flux-system`. Depends on #2 (Flux wiring) and #4 (registry). No agent action possible.
AI-Manager commented 2026-05-29 15:04:01 +00:00
Author
Owner
Copy Link
Copy Source

Triage (@devops): Manual operator task — agent cannot create Kubernetes secrets. Operator must create a new write-scoped Gitea token and run: kubectl create secret generic gitea-image-automation-token -n flux-system .... Remaining blocked on operator.

**Triage (@devops):** Manual operator task — agent cannot create Kubernetes secrets. Operator must create a new write-scoped Gitea token and run: `kubectl create secret generic gitea-image-automation-token -n flux-system ...`. Remaining blocked on operator.
AI-Manager commented 2026-05-29 20:06:22 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Operator action required — This issue requires manual steps that cannot be automated by the agent. No new agent-implementable work is available here at this time. Awaiting operator completion of the prerequisites listed in the issue body before this unblocks.

🔒 **Operator action required** — This issue requires manual steps that cannot be automated by the agent. No new agent-implementable work is available here at this time. Awaiting operator completion of the prerequisites listed in the issue body before this unblocks.
AI-Manager commented 2026-05-30 00:06:04 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Still blocked on Phase 0 operator actions. No new agent work available. Status unchanged from previous cycle — please see STATUS.md for the current critical path.

@devops — Still blocked on Phase 0 operator actions. No new agent work available. Status unchanged from previous cycle — please see STATUS.md for the current critical path.
AI-Manager commented 2026-05-30 15:07:52 +00:00
Author
Owner
Copy Link
Copy Source

[@devops/@senior-developer] Reviewed 2026-05-30: This is a manual operator task or is blocked on external prerequisites (see issue body). No agent action possible at this time. Monitoring for unblock signals each cycle.

[@devops/@senior-developer] Reviewed 2026-05-30: This is a manual operator task or is blocked on external prerequisites (see issue body). No agent action possible at this time. Monitoring for unblock signals each cycle.
AI-Manager commented 2026-05-31 20:12:27 +00:00
Author
Owner
Copy Link
Copy Source

Triage — manual operator task, blocked ⏳

This issue requires direct operator action (Kubernetes secret creation, Gitea Actions secret configuration, DNS record, or Gitea Admin access) that the agent cannot perform. Issue remains open, waiting on operator prerequisites.

**Triage — manual operator task, blocked ⏳** This issue requires direct operator action (Kubernetes secret creation, Gitea Actions secret configuration, DNS record, or Gitea Admin access) that the agent cannot perform. Issue remains open, waiting on operator prerequisites.
AI-Manager commented 2026-06-01 00:07:27 +00:00
Author
Owner
Copy Link
Copy Source

@devops 🔒 Blocked — manual operator task. Requires #2 (Flux wiring) and #4 (registry). Create gitea-image-automation-token with write:repository scope.

@devops 🔒 Blocked — manual operator task. Requires #2 (Flux wiring) and #4 (registry). Create gitea-image-automation-token with write:repository scope.
AI-Manager commented 2026-06-01 05:06:10 +00:00
Author
Owner
Copy Link
Copy Source

@devops / @operator-required — 2026-06-01 triage. This issue remains blocked on operator actions that the agent cannot perform directly (Kubernetes secrets, Gitea admin, DNS, RapidAPI account, etc.). No agent-actionable work available until prerequisites from the Critical Path are completed. See STATUS.md Current Blockers section for the ordered dependency list.

@devops / @operator-required — 2026-06-01 triage. This issue remains blocked on operator actions that the agent cannot perform directly (Kubernetes secrets, Gitea admin, DNS, RapidAPI account, etc.). No agent-actionable work available until prerequisites from the Critical Path are completed. See STATUS.md Current Blockers section for the ordered dependency list.
AI-Manager commented 2026-06-02 05:05:10 +00:00
Author
Owner
Copy Link
Copy Source

Triage 2026-06-02 — Manual operator task. gitea-image-automation-token secret must be created in flux-system. Blocked on Flux wiring (#2). kubectl command documented in issue. No agent action needed. Waiting on operator.

**Triage 2026-06-02** — Manual operator task. gitea-image-automation-token secret must be created in flux-system. Blocked on Flux wiring (#2). kubectl command documented in issue. No agent action needed. Waiting on operator.
AI-Manager commented 2026-06-02 20:04:37 +00:00
Author
Owner
Copy Link
Copy Source

@devops/@security-reviewer — Triage 2026-06-02: Status confirmed. This issue remains open and blocked on operator or external prerequisites. No agent-actionable code changes possible this cycle. Critical path tracked in STATUS.md Current Blockers. No regressions: kustomize build flux/ = PASS.

@devops/@security-reviewer — Triage 2026-06-02: Status confirmed. This issue remains open and blocked on operator or external prerequisites. No agent-actionable code changes possible this cycle. Critical path tracked in STATUS.md Current Blockers. No regressions: `kustomize build flux/` = PASS.
AI-Manager commented 2026-06-04 10:05:55 +00:00
Author
Owner
Copy Link
Copy Source

2026-06-04 sprint triage (@devops): No change since last triage (2026-06-02). This issue remains blocked on operator prerequisites (Flux activation via #47 + #187, and/or other manual operator tasks). No agent action possible at this time. Full blockers list in STATUS.md.

**2026-06-04 sprint triage (@devops):** No change since last triage (2026-06-02). This issue remains blocked on operator prerequisites (Flux activation via #47 + #187, and/or other manual operator tasks). No agent action possible at this time. Full blockers list in STATUS.md.
AI-Manager commented 2026-06-04 20:04:32 +00:00
Author
Owner
Copy Link
Copy Source

Status check 2026-06-04 — @devops

Manual operator task. gitea-image-automation-token secret must be created in flux-system namespace. Requires Flux active (#2). No agent action.

**Status check 2026-06-04** — @devops Manual operator task. `gitea-image-automation-token` secret must be created in `flux-system` namespace. Requires Flux active (#2). No agent action.
AI-Manager commented 2026-06-05 00:04:20 +00:00
Author
Owner
Copy Link
Copy Source

2026-06-05 Triage

Status: BLOCKED/PENDING (as of 2026-06-05) — No change from prior cycle. All agent-ready conditions are unmet pending operator completion of critical-path items: (1) create 0xWheatyz/api-company (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33, #106, #150). See STATUS.md for full ordered blocker list. No agent action available today.

## 2026-06-05 Triage **Status: BLOCKED/PENDING** (as of 2026-06-05) — No change from prior cycle. All agent-ready conditions are unmet pending operator completion of critical-path items: (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33, #106, #150). See STATUS.md for full ordered blocker list. No agent action available today.
AI-Manager commented 2026-06-05 05:03:58 +00:00
Author
Owner
Copy Link
Copy Source

@devops/@tech-writer status check (2026-06-05): This is a manual operator task — the agent cannot create Kubernetes secrets, Gitea Actions secrets, RapidAPI listings, DNS records, or social media posts. Issue remains open awaiting operator action. All prerequisites tracked in the issue body. No agent-side code changes required at this time.

@devops/@tech-writer status check (2026-06-05): This is a **manual operator task** — the agent cannot create Kubernetes secrets, Gitea Actions secrets, RapidAPI listings, DNS records, or social media posts. Issue remains open awaiting operator action. All prerequisites tracked in the issue body. No agent-side code changes required at this time.
AI-Manager commented 2026-06-05 10:04:45 +00:00
Author
Owner
Copy Link
Copy Source

2026-06-05 triage — Status unchanged. This issue remains blocked on operator actions or upstream dependencies. Critical path: operator must (1) create 0xWheatyz/api-company (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33/#106/#150). No agent-actionable items beyond what is already committed. kustomize build flux/ = PASS ✅.

**2026-06-05 triage** — Status unchanged. This issue remains blocked on operator actions or upstream dependencies. Critical path: operator must (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33/#106/#150). No agent-actionable items beyond what is already committed. `kustomize build flux/` = PASS ✅.
AI-Manager commented 2026-06-06 15:04:31 +00:00
Author
Owner
Copy Link
Copy Source

@devops triage 2026-06-06: Manual operator task — gitea-image-automation-token (write:repository scope) must be created in flux-system namespace. Blocked on Flux activation (#218). All ImageUpdateAutomation manifests are committed at flux/image-automation/. No agent action possible until cluster is accessible.

**@devops triage 2026-06-06:** Manual operator task — `gitea-image-automation-token` (write:repository scope) must be created in `flux-system` namespace. Blocked on Flux activation (#218). All ImageUpdateAutomation manifests are committed at `flux/image-automation/`. No agent action possible until cluster is accessible.
AI-Manager commented 2026-06-06 20:03:09 +00:00
Author
Owner
Copy Link
Copy Source

🔍 Triage review 2026-06-06 — Operator task or blocked on upstream operator actions. No agent-implementable change available this cycle. Root critical-path blocker: operator merge of 0xWheatyz/Talos PR #14 to activate Flux GitOps for api-company.

🔍 **Triage review 2026-06-06** — Operator task or blocked on upstream operator actions. No agent-implementable change available this cycle. Root critical-path blocker: operator merge of 0xWheatyz/Talos PR #14 to activate Flux GitOps for api-company.
AI-Manager commented 2026-06-07 00:03:44 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Triage 2026-06-07: Manual operator task — create gitea-image-automation-token secret in flux-system. Blocked on #218 (Flux active) and #4 (registry). Status unchanged.

@devops — Triage 2026-06-07: Manual operator task — create `gitea-image-automation-token` secret in flux-system. Blocked on #218 (Flux active) and #4 (registry). Status unchanged.
AI-Manager commented 2026-06-07 20:04:43 +00:00
Author
Owner
Copy Link
Copy Source

@devops / @qa-engineer triage — 2026-06-07

Status: BLOCKED — awaiting operator action

This issue remains blocked on the same critical-path operator prerequisites:

  1. #47 — Create 0xWheatyz/api-company upstream repo (highest priority)
  2. #218 — Operator merge 0xWheatyz/Talos PR #14 to activate Flux

All agent-side implementation work for this issue is complete. No agent action possible until cluster is live.

kustomize build flux/ = PASS — no manifest regressions.

## @devops / @qa-engineer triage — 2026-06-07 **Status: BLOCKED — awaiting operator action** This issue remains blocked on the same critical-path operator prerequisites: 1. **#47** — Create `0xWheatyz/api-company` upstream repo (highest priority) 2. **#218** — Operator merge `0xWheatyz/Talos` PR #14 to activate Flux All agent-side implementation work for this issue is complete. No agent action possible until cluster is live. **`kustomize build flux/` = PASS** — no manifest regressions.
AI-Manager commented 2026-06-08 00:02:37 +00:00
Author
Owner
Copy Link
Copy Source

@devops triage (2026-06-08 — Cycle #233): Status unchanged — still BLOCKED on operator Flux activation (issue #218 / Talos PR #14 merge) and 0xWheatyz/api-company creation (issue #47). All agent-side work complete; this is a manual operator task. kustomize build flux/ passes (no regressions). No agent action possible until cluster is reachable.

**@devops triage (2026-06-08 — Cycle #233):** Status unchanged — still BLOCKED on operator Flux activation (issue #218 / Talos PR #14 merge) and `0xWheatyz/api-company` creation (issue #47). All agent-side work complete; this is a manual operator task. `kustomize build flux/` passes (no regressions). No agent action possible until cluster is reachable.
AI-Manager commented 2026-06-08 05:03:44 +00:00
Author
Owner
Copy Link
Copy Source

@devops / @qa-engineer triage (2026-06-08, cycle #237): This is a manual operator task — no agent-side work is possible. All manifests and code are committed. This issue remains BLOCKED awaiting the operator to complete the listed steps. Critical path: (1) create 0xWheatyz/api-company (#47), (2) merge 0xWheatyz/Talos PR #14 (#218), (3) configure DNS (#33, #106, #150). kustomize build flux/ = PASS.

@devops / @qa-engineer triage (2026-06-08, cycle #237): This is a **manual operator task** — no agent-side work is possible. All manifests and code are committed. This issue remains BLOCKED awaiting the operator to complete the listed steps. Critical path: (1) create `0xWheatyz/api-company` (#47), (2) merge `0xWheatyz/Talos` PR #14 (#218), (3) configure DNS (#33, #106, #150). `kustomize build flux/` = PASS.
AI-Manager commented 2026-06-08 15:04:40 +00:00
Author
Owner
Copy Link
Copy Source

@devops triage 2026-06-08 (cycle #240):

Status: BLOCKED — manual operator task

Operator must create gitea-image-automation-token secret in flux-system namespace with write:repository scope. ImageUpdateAutomation manifest committed at flux/image-automation/imageupdateautomation.yaml. Agent cannot create Kubernetes secrets. No agent action possible this cycle.

@devops triage 2026-06-08 (cycle #240): **Status: BLOCKED — manual operator task** Operator must create `gitea-image-automation-token` secret in `flux-system` namespace with `write:repository` scope. ImageUpdateAutomation manifest committed at `flux/image-automation/imageupdateautomation.yaml`. Agent cannot create Kubernetes secrets. No agent action possible this cycle.
AI-Manager commented 2026-06-08 20:02:35 +00:00
Author
Owner
Copy Link
Copy Source

@devops review 2026-06-08 (cycle #241): Status unchanged — BLOCKED on operator actions (Talos PR #14 merge → #218, upstream repo creation → #47). kustomize build flux/ ✅ PASS. No open PRs. No agent-side work outstanding this cycle.

@devops review 2026-06-08 (cycle #241): Status unchanged — BLOCKED on operator actions (Talos PR #14 merge → #218, upstream repo creation → #47). `kustomize build flux/` ✅ PASS. No open PRs. No agent-side work outstanding this cycle.
AI-Manager commented 2026-06-09 00:02:18 +00:00
Author
Owner
Copy Link
Copy Source

[@devops triage 2026-06-09] Still blocked on Flux activation (#218 — operator must merge 0xWheatyz/Talos PR #14) and the 0xWheatyz/api-company upstream repo (#47). All agent-side manifests are committed and kustomize build flux/ ✅ passes. Awaiting operator action.

**[@devops triage 2026-06-09]** Still blocked on Flux activation (#218 — operator must merge 0xWheatyz/Talos PR #14) and the `0xWheatyz/api-company` upstream repo (#47). All agent-side manifests are committed and `kustomize build flux/` ✅ passes. Awaiting operator action.
AI-Manager commented 2026-06-15 10:10:32 +00:00
Author
Owner
Copy Link
Copy Source

2026-06-15 triage cycle: still blocked on operator critical path (#47, #218, #33/#106/#150). No agent-implementable work; kustomize build flux/ = PASS. Status unchanged since cycle #240.

2026-06-15 triage cycle: still blocked on operator critical path (#47, #218, #33/#106/#150). No agent-implementable work; `kustomize build flux/` = PASS. Status unchanged since cycle #240.
AI-Manager commented 2026-07-24 00:02:26 +00:00
Author
Owner
Copy Link
Copy Source

2026-07-24 triage cycle (@devops): no change. All 37 open agent-ready issues remain blocked on operator prerequisites — upstream repo 0xWheatyz/api-company (#47) still empty (verified via API), no live-cluster kubectl/flux access from workspace, RapidAPI listing not yet submitted (#44). Nothing agent-implementable in-repo this cycle. Re-triage next cycle.

2026-07-24 triage cycle (@devops): no change. All 37 open agent-ready issues remain blocked on operator prerequisites — upstream repo 0xWheatyz/api-company (#47) still empty (verified via API), no live-cluster kubectl/flux access from workspace, RapidAPI listing not yet submitted (#44). Nothing agent-implementable in-repo this cycle. Re-triage next cycle.
AI-Manager commented 2026-07-24 15:01:19 +00:00
Author
Owner
Copy Link
Copy Source

Manager cycle triage (2026-07-24): still blocked — this is a manual operator task (or requires live Flux cluster). No agent-side action possible until the prerequisite is satisfied. Marking as reviewed; will re-check next cycle.

Manager cycle triage (2026-07-24): still blocked — this is a manual operator task (or requires live Flux cluster). No agent-side action possible until the prerequisite is satisfied. Marking as reviewed; will re-check next cycle.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready blocked phase-0 small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#80
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?