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

[Phase 0] Operator: create gitea-leeworks-agents-token secret in flux-system to unblock Flux GitRepository auth #76

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

Problem

The Flux GitRepository source for leeworks-agents/api-company (manifests at flux/api-company-source/) requires a Kubernetes secret named gitea-leeworks-agents-token in the flux-system namespace. Without it, Flux cannot authenticate to Gitea over HTTPS and the api-company GitRepository will never become READY=True.

This is blocker #3 in STATUS.md and item #1 in docs/secrets-checklist.md, but it has no dedicated tracking issue — it is currently buried inside issue #2 (the broader Flux wiring task). This issue gives it its own trackable entry, consistent with #70 (grafana-admin), #73 (gatus-slack-webhook), and #74 (GITEA_TOKEN).

What the operator must do

  1. Generate a Gitea personal access token for the leeworks-agents user:

    • Gitea → User Settings → Applications → Generate Token
    • Scopes: read:repository
    • Save the token somewhere safe

  2. Create the secret in the cluster:

kubectl create secret generic gitea-leeworks-agents-token \
  -n flux-system \
  --from-literal=username=leeworks-agents \
  --from-literal=password=<GITEA_TOKEN>
  1. Verify it exists:
kubectl get secret gitea-leeworks-agents-token -n flux-system
  1. Trigger Flux reconciliation of the api-company source:
flux reconcile source git api-company

Acceptance criteria

  • kubectl get secret gitea-leeworks-agents-token -n flux-system returns the secret
  • flux get sources git api-company shows READY=True
  • flux get kustomizations api-company shows READY=True (once Talos PR from #2 is merged)

Dependencies

Note

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

(Reference: ROADMAP.md §Phase 0; docs/secrets-checklist.md item #1; STATUS.md Blockers #3)

## Problem The Flux `GitRepository` source for `leeworks-agents/api-company` (manifests at `flux/api-company-source/`) requires a Kubernetes secret named `gitea-leeworks-agents-token` in the `flux-system` namespace. Without it, Flux cannot authenticate to Gitea over HTTPS and the `api-company` GitRepository will never become `READY=True`. This is **blocker #3** in `STATUS.md` and item #1 in `docs/secrets-checklist.md`, but it has no dedicated tracking issue — it is currently buried inside issue #2 (the broader Flux wiring task). This issue gives it its own trackable entry, consistent with #70 (grafana-admin), #73 (gatus-slack-webhook), and #74 (GITEA_TOKEN). ## What the operator must do 1. Generate a Gitea personal access token for the `leeworks-agents` user: - Gitea → User Settings → Applications → Generate Token - Scopes: `read:repository` - Save the token somewhere safe 2. Create the secret in the cluster: ```bash kubectl create secret generic gitea-leeworks-agents-token \ -n flux-system \ --from-literal=username=leeworks-agents \ --from-literal=password=<GITEA_TOKEN> ``` 3. Verify it exists: ```bash kubectl get secret gitea-leeworks-agents-token -n flux-system ``` 4. Trigger Flux reconciliation of the api-company source: ```bash flux reconcile source git api-company ``` ## Acceptance criteria - `kubectl get secret gitea-leeworks-agents-token -n flux-system` returns the secret - `flux get sources git api-company` shows `READY=True` - `flux get kustomizations api-company` shows `READY=True` (once Talos PR from #2 is merged) ## Dependencies - Depends on leeworks-agents/api-company#47 (upstream `0xWheatyz/api-company` repo must exist first) - Depends on leeworks-agents/api-company#2 (Talos PR must add the `api-company` GitRepository + Kustomization manifests) - Unblocks leeworks-agents/api-company#2, #3, #4, #7, #8 (all require Flux to be active) ## Note This is a **manual operator task** — the agent cannot create Kubernetes secrets directly. _(Reference: ROADMAP.md §Phase 0; docs/secrets-checklist.md item #1; STATUS.md Blockers #3)_
AI-Manager added the agent-readyblockedphase-0P1small labels 2026-05-28 05:23:04 +00:00
AI-Manager commented 2026-05-28 10:01:54 +00:00
Author
Owner
Copy Link
Copy Source

Triage — @devops / 2026-05-28 (night cycle)

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

Status: Awaiting operator action. All prerequisites are clearly documented.

Summary of action needed:

  1. Generate a Gitea PAT for the leeworks-agents user (scope: read:repository) via Gitea → User Settings → Applications → Generate Token
  2. Run:
kubectl create secret generic gitea-leeworks-agents-token \
  -n flux-system \
  --from-literal=username=leeworks-agents \
  --from-literal=password=<GITEA_TOKEN>
  1. Trigger reconcile: flux reconcile source git api-company

This is blocker #3 in STATUS.md. Once completed it unblocks Flux wiring for the entire api-company GitOps pipeline (issues #2, #3, #4, #7, #8).

No agent-implementable work exists here. Issue remains open until operator confirms completion.

**Triage — @devops / 2026-05-28 (night cycle)** This is a **manual operator task** — the agent cannot create Kubernetes secrets directly. **Status:** Awaiting operator action. All prerequisites are clearly documented. **Summary of action needed:** 1. Generate a Gitea PAT for the `leeworks-agents` user (scope: `read:repository`) via Gitea → User Settings → Applications → Generate Token 2. Run: ```bash kubectl create secret generic gitea-leeworks-agents-token \ -n flux-system \ --from-literal=username=leeworks-agents \ --from-literal=password=<GITEA_TOKEN> ``` 3. Trigger reconcile: `flux reconcile source git api-company` This is **blocker #3** in `STATUS.md`. Once completed it unblocks Flux wiring for the entire api-company GitOps pipeline (issues #2, #3, #4, #7, #8). No agent-implementable work exists here. Issue remains open until operator confirms completion.
AI-Manager commented 2026-05-29 10:03:10 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Triaged. This is a manual operator task. The agent cannot create Kubernetes secrets. Status: blocked on operator action — operator must create gitea-leeworks-agents-token in flux-system namespace. Also depends on #90 (Talos PR adding the api-company Flux source manifests). No agent action possible.

**@devops** — Triaged. This is a manual operator task. The agent cannot create Kubernetes secrets. Status: **blocked on operator action** — operator must create `gitea-leeworks-agents-token` in `flux-system` namespace. Also depends on #90 (Talos PR adding the api-company Flux source manifests). No agent action possible.
AI-Manager commented 2026-05-29 15:04:09 +00:00
Author
Owner
Copy Link
Copy Source

Triage (@devops): Manual operator task — agent cannot create Kubernetes secrets. Operator must generate a read:repository Gitea token and kubectl create secret generic gitea-leeworks-agents-token -n flux-system .... This is blocker #3 in STATUS.md. Remaining blocked on operator.

**Triage (@devops):** Manual operator task — agent cannot create Kubernetes secrets. Operator must generate a `read:repository` Gitea token and `kubectl create secret generic gitea-leeworks-agents-token -n flux-system ...`. This is blocker #3 in STATUS.md. 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:02 +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:54 +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:28 +00:00
Author
Owner
Copy Link
Copy Source

@devops 🔒 Blocked — manual operator task. Requires #47 (upstream repo) and #2 (Talos PR). Create gitea-leeworks-agents-token in flux-system namespace.

@devops 🔒 Blocked — manual operator task. Requires #47 (upstream repo) and #2 (Talos PR). Create gitea-leeworks-agents-token in flux-system namespace.
AI-Manager commented 2026-06-01 05:06:11 +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:23 +00:00
Author
Owner
Copy Link
Copy Source

Triage 2026-06-02 — Manual operator task. gitea-leeworks-agents-token secret must be created in flux-system namespace. kubectl command documented in issue. Blocked on upstream repo (#47) and Talos PR (#2). No agent action needed. Waiting on operator.

**Triage 2026-06-02** — Manual operator task. gitea-leeworks-agents-token secret must be created in flux-system namespace. kubectl command documented in issue. Blocked on upstream repo (#47) and Talos PR (#2). No agent action needed. Waiting on operator.
AI-Manager commented 2026-06-02 20:04:38 +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:08 +00:00
Author
Owner
Copy Link
Copy Source

2026-06-04 sprint triage (@devops): No change since last triage. This is a manual operator task — waiting on operator completion of #47 (upstream repo) and Talos PR merge (#187) before Flux can activate. Instructions remain accurate in the issue body.

**2026-06-04 sprint triage (@devops):** No change since last triage. This is a manual operator task — waiting on operator completion of #47 (upstream repo) and Talos PR merge (#187) before Flux can activate. Instructions remain accurate in the issue body.
AI-Manager commented 2026-06-04 20:04:54 +00:00
Author
Owner
Copy Link
Copy Source

Status check 2026-06-04 — @devops

Manual operator task. gitea-leeworks-agents-token secret must be created in flux-system namespace. This is the critical auth secret for Flux GitRepository. Blocked on Talos PR #14 merge (#187). No agent action.

**Status check 2026-06-04** — @devops Manual operator task. `gitea-leeworks-agents-token` secret must be created in `flux-system` namespace. This is the critical auth secret for Flux GitRepository. Blocked on Talos PR #14 merge (#187). No agent action.
AI-Manager commented 2026-06-05 00:04:21 +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:04:00 +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:45 +00:00
Author
Owner
Copy Link
Copy Source

@devops triage 2026-06-06: Manual operator task — gitea-leeworks-agents-token (read:repository scope) must be created in flux-system namespace to enable Flux GitRepository auth. This is the first secret to create once cluster is accessible. Blocked on #47 (upstream repo must exist first) and #218 (Talos Flux manifests).

**@devops triage 2026-06-06:** Manual operator task — `gitea-leeworks-agents-token` (read:repository scope) must be created in `flux-system` namespace to enable Flux GitRepository auth. This is the first secret to create once cluster is accessible. Blocked on #47 (upstream repo must exist first) and #218 (Talos Flux manifests).
AI-Manager commented 2026-06-06 20:03:10 +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:55 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Triage 2026-06-07: Manual operator task — create gitea-leeworks-agents-token secret in flux-system. Blocked on #218 (operator must merge Talos PR #14 first to activate Flux). Status unchanged.

@devops — Triage 2026-06-07: Manual operator task — create `gitea-leeworks-agents-token` secret in flux-system. Blocked on #218 (operator must merge Talos PR #14 first to activate Flux). Status unchanged.
AI-Manager commented 2026-06-07 20:04:46 +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:29 +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:42 +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:56 +00:00
Author
Owner
Copy Link
Copy Source

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

Status: BLOCKED — manual operator task (P1)

Operator must create gitea-leeworks-agents-token secret in flux-system namespace using a Gitea PAT with read:repository scope. This is the critical blocker for Flux GitRepository auth. Steps documented in issue body. Agent cannot create Kubernetes secrets. No agent action possible this cycle.

@devops triage 2026-06-08 (cycle #240): **Status: BLOCKED — manual operator task (P1)** Operator must create `gitea-leeworks-agents-token` secret in `flux-system` namespace using a Gitea PAT with `read:repository` scope. This is the critical blocker for Flux GitRepository auth. Steps documented in issue body. Agent cannot create Kubernetes secrets. No agent action possible this cycle.
AI-Manager commented 2026-06-08 20:02:27 +00:00
Author
Owner
Copy Link
Copy Source

@devops review 2026-06-08 (cycle #241):

Status: BLOCKED — depends on #47 (upstream repo) + #218 (Flux activation)

No change from prior cycle. Upstream repo 0xWheatyz/api-company still does not exist (HTTP 404). Once the operator creates the repo (#47) and merges Talos PR #14 (#218), this secret can be created and Flux GitRepository auth will activate.

No agent-side work outstanding.

@devops review 2026-06-08 (cycle #241): **Status: BLOCKED — depends on #47 (upstream repo) + #218 (Flux activation)** No change from prior cycle. Upstream repo 0xWheatyz/api-company still does not exist (HTTP 404). Once the operator creates the repo (#47) and merges Talos PR #14 (#218), this secret can be created and Flux GitRepository auth will activate. No agent-side work outstanding.
AI-Manager commented 2026-06-09 00:02:00 +00:00
Author
Owner
Copy Link
Copy Source

[@devops triage 2026-06-09] Blocked on #218 (Flux not yet active — operator must merge 0xWheatyz/Talos PR #14). Once Flux is active, operator must create the gitea-leeworks-agents-token secret in flux-system namespace to unblock the GitRepository auth. No agent action possible.

**[@devops triage 2026-06-09]** Blocked on #218 (Flux not yet active — operator must merge 0xWheatyz/Talos PR #14). Once Flux is active, operator must create the `gitea-leeworks-agents-token` secret in `flux-system` namespace to unblock the GitRepository auth. No agent action possible.
AI-Manager commented 2026-06-15 10:10:29 +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:27 +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:20 +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.
AI-Manager commented 2026-07-27 00:02:07 +00:00
Author
Owner
Copy Link
Copy Source

Triage 2026-07-27 (@devops): still blocked on operator prerequisite. No agent-actionable change possible until the manual step is completed. Re-checked; no state change.

Triage 2026-07-27 (@devops): still blocked on operator prerequisite. No agent-actionable change possible until the manual step is completed. Re-checked; no state change.
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 P1 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#76
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?