Activate westside-contracts in Woodpecker CI #3

New issue

Closed

opened 2026-03-24 15:53:43 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-24 15:53:43 +00:00

Owner

Type

Feature

Lineage

plan-wkq → Phase 14 → CI setup

Repo

forgejo_admin/westside-contracts

User Story

As a platform operator
I want westside-contracts to have a CI pipeline
So that builds and tests run automatically on push

Context

Repo was deployed manually (docker build + push). Woodpecker doesn't have the repo activated. .woodpecker.yml exists in the repo but isn't wired.

File Targets

Woodpecker admin: activate forgejo_admin/westside-contracts
Verify .woodpecker.yml pipeline runs successfully

Acceptance Criteria

Repo activated in Woodpecker
Push to main triggers pipeline
Tests run, image builds and pushes to Harbor

Test Expectations

Push a commit, verify pipeline runs
Run command: check Woodpecker UI

Constraints

Follow existing repo activation pattern

Checklist

Activated
Pipeline green

project-westside-basketball
westside-app #72

### Type Feature ### Lineage `plan-wkq` → Phase 14 → CI setup ### Repo `forgejo_admin/westside-contracts` ### User Story As a platform operator I want westside-contracts to have a CI pipeline So that builds and tests run automatically on push ### Context Repo was deployed manually (docker build + push). Woodpecker doesn't have the repo activated. `.woodpecker.yml` exists in the repo but isn't wired. ### File Targets - Woodpecker admin: activate `forgejo_admin/westside-contracts` - Verify `.woodpecker.yml` pipeline runs successfully ### Acceptance Criteria - [ ] Repo activated in Woodpecker - [ ] Push to main triggers pipeline - [ ] Tests run, image builds and pushes to Harbor ### Test Expectations - [ ] Push a commit, verify pipeline runs - Run command: check Woodpecker UI ### Constraints - Follow existing repo activation pattern ### Checklist - [ ] Activated - [ ] Pipeline green ### Related - `project-westside-basketball` - westside-app #72