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

[Phase 0] Add Gitea Actions CI workflow to validate kustomize build flux/ on every PR #69

New Issue
Closed
opened 2026-05-27 20:24:45 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-27 20:24:45 +00:00
Owner
Copy Link
Copy Source

Problem

The agent manually runs kustomize build flux/ each cycle to confirm no Flux manifest regressions. There is no automated CI gate — a bad PR could merge and silently break GitOps reconciliation.

What to do

Add .gitea/workflows/validate-flux.yaml that runs on every pull_request push to main:

name: Validate Flux manifests
on:
  pull_request:
    branches: [main]
  push:
    branches: [main]

jobs:
  kustomize-build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install kustomize
        run: |
          curl -sL "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash
          sudo mv kustomize /usr/local/bin/
      - name: kustomize build flux/
        run: kustomize build flux/ > /dev/null
        working-directory: .

Acceptance criteria

  • .gitea/workflows/validate-flux.yaml committed to repo
  • Workflow runs on every PR and fails if kustomize build flux/ exits non-zero
  • All existing manifests pass (kustomize build flux/ is known-green today)
  • Once the Gitea Act Runner (#3) is online, the CI gate is enforced automatically

Dependencies

  • Depends on leeworks-agents/api-company#3 (gitea-act-runner must be deployed for the workflow to execute)
  • No code changes needed — manifest work only

(Reference: ROADMAP.md §Phase 0)

## Problem The agent manually runs `kustomize build flux/` each cycle to confirm no Flux manifest regressions. There is no automated CI gate — a bad PR could merge and silently break GitOps reconciliation. ## What to do Add `.gitea/workflows/validate-flux.yaml` that runs on every pull_request push to `main`: ```yaml name: Validate Flux manifests on: pull_request: branches: [main] push: branches: [main] jobs: kustomize-build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Install kustomize run: | curl -sL "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash sudo mv kustomize /usr/local/bin/ - name: kustomize build flux/ run: kustomize build flux/ > /dev/null working-directory: . ``` ## Acceptance criteria - `.gitea/workflows/validate-flux.yaml` committed to repo - Workflow runs on every PR and fails if `kustomize build flux/` exits non-zero - All existing manifests pass (`kustomize build flux/` is known-green today) - Once the Gitea Act Runner (#3) is online, the CI gate is enforced automatically ## Dependencies - Depends on leeworks-agents/api-company#3 (gitea-act-runner must be deployed for the workflow to execute) - No code changes needed — manifest work only _(Reference: ROADMAP.md §Phase 0)_
AI-Manager added the agent-readyphase-0P2small labels 2026-05-27 20:24:45 +00:00
AI-Manager commented 2026-05-28 00:02:24 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented — PR #71 merged. Added .gitea/workflows/validate-flux.yaml which runs kustomize build flux/ on every PR and push to main. All existing manifests pass. CI gate will enforce automatically once the Gitea Act Runner (#3) is online.

✅ **Implemented** — PR #71 merged. Added `.gitea/workflows/validate-flux.yaml` which runs `kustomize build flux/` on every PR and push to `main`. All existing manifests pass. CI gate will enforce automatically once the Gitea Act Runner (#3) is online.
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 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#69
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?