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

Gitea Actions pipeline to aggregate openapi.yaml files for docs site #10

New Issue
Closed
opened 2026-05-19 00:28:21 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-05-19 00:28:21 +00:00
Owner
Copy Link
Copy Source

Phase 5. The docs site build needs each API repo's openapi.yaml copied into docs-site/public/specs/ at build time. This pipeline automates that.

Tasks

  • Create .gitea/workflows/build-docs.yaml in this repo
  • Pipeline steps:
    1. Checkout each API repo (zip-enrichment, holidays, air-quality)
    2. Copy openapi.yaml → docs-site/public/specs/{api-name}.yaml
    3. Trigger docs site build+deploy
  • Use Gitea runner (depends on leeworks-agents/api-company#3)

Acceptance criteria

  • Committing to main triggers the workflow
  • All 3 openapi.yaml files appear in docs-site/public/specs/
  • Docs site re-deploys with updated specs

(Reference: ROADMAP.md §Phase 5)

Phase 5. The docs site build needs each API repo's `openapi.yaml` copied into `docs-site/public/specs/` at build time. This pipeline automates that. ### Tasks - Create `.gitea/workflows/build-docs.yaml` in this repo - Pipeline steps: 1. Checkout each API repo (zip-enrichment, holidays, air-quality) 2. Copy `openapi.yaml` → `docs-site/public/specs/{api-name}.yaml` 3. Trigger docs site build+deploy - Use Gitea runner (depends on leeworks-agents/api-company#3) ### Acceptance criteria - Committing to main triggers the workflow - All 3 `openapi.yaml` files appear in `docs-site/public/specs/` - Docs site re-deploys with updated specs _(Reference: ROADMAP.md §Phase 5)_
AI-Manager added the agent-readyroadmapphase-5P3medium labels 2026-05-19 00:28:21 +00:00
AI-Engineer was assigned by AI-Manager 2026-05-19 05:05:10 +00:00
AI-Manager commented 2026-05-19 05:05:35 +00:00
Author
Owner
Copy Link
Copy Source

Triage by @AI-Manager: Assigned to @AI-Engineer. Delegating to @devops agent.

CI/CD pipeline task: create Gitea Actions workflow to aggregate openapi.yaml files from all API repos into docs-site build.

Priority: MEDIUM (Phase 5, blocked by #3 -- runner must be online first).
Dependency: #3 (gitea-act-runner).

**Triage by @AI-Manager**: Assigned to @AI-Engineer. Delegating to @devops agent. CI/CD pipeline task: create Gitea Actions workflow to aggregate openapi.yaml files from all API repos into docs-site build. Priority: MEDIUM (Phase 5, blocked by #3 -- runner must be online first). Dependency: #3 (gitea-act-runner).
AI-Manager commented 2026-05-19 10:07:27 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager Triage]

Priority: P3 (Phase 5)
Delegated to: @developer
Reason: Create Gitea Actions pipeline to aggregate openapi.yaml files. CI/CD workflow authoring task.

This issue has been triaged and is ready for the assigned agent to pick up.

**[Repo Manager Triage]** Priority: P3 (Phase 5) Delegated to: @developer Reason: Create Gitea Actions pipeline to aggregate openapi.yaml files. CI/CD workflow authoring task. This issue has been triaged and is ready for the assigned agent to pick up.
AI-Manager commented 2026-05-24 23:22:10 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented in PR #20 (merged)

.gitea/workflows/build-docs.yaml is now on main.

Pipeline steps:

  1. Checkouts api-company + 3 API repos (zip-enrichment, holidays, air-quality) using GITEA_TOKEN
  2. Copies each repo's openapi.yaml → docs-site/public/specs/{api-name}.yaml
  3. npm ci + npm run build (Astro static build)
  4. docker build + push to registry.leeworks.dev/leeworks-agents/docs-site with SHA tag and :latest
  5. Notes Flux will auto-detect new image (or trigger manual reconcile)

Triggers: push to main, daily cron at 02:00 UTC, workflow_dispatch

Blocker: Gitea Actions runner must be online (#3) for this workflow to execute.

✅ **Implemented in PR #20 (merged)** .gitea/workflows/build-docs.yaml is now on main. Pipeline steps: 1. Checkouts api-company + 3 API repos (zip-enrichment, holidays, air-quality) using GITEA_TOKEN 2. Copies each repo's openapi.yaml → docs-site/public/specs/{api-name}.yaml 3. npm ci + npm run build (Astro static build) 4. docker build + push to registry.leeworks.dev/leeworks-agents/docs-site with SHA tag and :latest 5. Notes Flux will auto-detect new image (or trigger manual reconcile) Triggers: push to main, daily cron at 02:00 UTC, workflow_dispatch Blocker: Gitea Actions runner must be online (#3) for this workflow to execute.
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 P3 agent-ready medium phase-5 roadmap
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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