Rename westside-app repo to westside-landing on Forgejo #147

New issue

Open

opened 2026-03-28 19:08:30 +00:00 by forgejo_admin · 2 comments

forgejo_admin commented

2026-03-28 19:08:30 +00:00

Owner

Type

Feature

Lineage

Sub-ticket of forgejo_admin/westside-app#109 (Landing site rename — decomposed).

Repo

forgejo_admin/westside-app

User Story

As a superadmin
I want the Forgejo repo renamed from westside-app to westside-landing
So that the repo name reflects the public landing site and frees westside-app for the auth portal.

Context

This is sub-ticket 1 of 4 from the decomposed #109 rename. This ticket covers ONLY the Forgejo API rename operation and post-rename verification of Woodpecker CI. No code changes — purely API + webhook verification.

The rename must happen FIRST, before sub-tickets 2-4 can proceed (they reference the new repo name).

Blocker: In-progress items #534 and #529 on board-westside-basketball must complete before this rename. Renaming while branches are open will break their CI pipelines.

File Targets

Files the agent should modify:

Forgejo repo settings — rename via PATCH /api/v1/repos/forgejo_admin/westside-app with {"name": "westside-landing"}

Files the agent should NOT touch:

Any code files — no code changes in this ticket
.woodpecker.yaml — ${CI_REPO} auto-adjusts after rename

Acceptance Criteria

Repo renamed to westside-landing on Forgejo via API
Woodpecker webhook still functional (auto-redirects on Forgejo rename)
CI pipeline triggers on a no-op push under the new name
Site remains live at westsidekingsandqueens.tail5b443a.ts.net (rename doesn't affect runtime)

Test Expectations

Manual: push a no-op commit to westside-landing, verify Woodpecker pipeline triggers
Manual: verify westsidekingsandqueens.tail5b443a.ts.net still serves pages
Run command: curl -s -o /dev/null -w '%{http_code}' https://westsidekingsandqueens.tail5b443a.ts.net/

Constraints

Must complete before sub-tickets 2-4 begin
Blocked by in-progress items #534 and #529
Woodpecker webhook URL changes automatically on Forgejo repo rename — verify, don't fight it
${CI_REPO} in .woodpecker.yaml auto-adjusts — no code change needed

Checklist

Rename executed via Forgejo API
Woodpecker webhook verified
No-op push triggers CI
No unrelated changes

forgejo_admin/westside-app#109 — parent ticket (decomposed)
Sub-ticket 2: pal-e-services terraform updates
Sub-ticket 3: pal-e-deployments overlay updates
Sub-ticket 4: pal-e-platform monitoring probe update
project-westside-basketball

### Type Feature ### Lineage Sub-ticket of `forgejo_admin/westside-app#109` (Landing site rename — decomposed). ### Repo `forgejo_admin/westside-app` ### User Story As a superadmin I want the Forgejo repo renamed from `westside-app` to `westside-landing` So that the repo name reflects the public landing site and frees `westside-app` for the auth portal. ### Context This is sub-ticket 1 of 4 from the decomposed `#109` rename. This ticket covers ONLY the Forgejo API rename operation and post-rename verification of Woodpecker CI. No code changes — purely API + webhook verification. The rename must happen FIRST, before sub-tickets 2-4 can proceed (they reference the new repo name). **Blocker:** In-progress items #534 and #529 on `board-westside-basketball` must complete before this rename. Renaming while branches are open will break their CI pipelines. ### File Targets Files the agent should modify: - Forgejo repo settings — rename via `PATCH /api/v1/repos/forgejo_admin/westside-app` with `{"name": "westside-landing"}` Files the agent should NOT touch: - Any code files — no code changes in this ticket - `.woodpecker.yaml` — `${CI_REPO}` auto-adjusts after rename ### Acceptance Criteria - [ ] Repo renamed to `westside-landing` on Forgejo via API - [ ] Woodpecker webhook still functional (auto-redirects on Forgejo rename) - [ ] CI pipeline triggers on a no-op push under the new name - [ ] Site remains live at `westsidekingsandqueens.tail5b443a.ts.net` (rename doesn't affect runtime) ### Test Expectations - [ ] Manual: push a no-op commit to `westside-landing`, verify Woodpecker pipeline triggers - [ ] Manual: verify `westsidekingsandqueens.tail5b443a.ts.net` still serves pages - Run command: `curl -s -o /dev/null -w '%{http_code}' https://westsidekingsandqueens.tail5b443a.ts.net/` ### Constraints - Must complete before sub-tickets 2-4 begin - Blocked by in-progress items #534 and #529 - Woodpecker webhook URL changes automatically on Forgejo repo rename — verify, don't fight it - `${CI_REPO}` in `.woodpecker.yaml` auto-adjusts — no code change needed ### Checklist - [ ] Rename executed via Forgejo API - [ ] Woodpecker webhook verified - [ ] No-op push triggers CI - [ ] No unrelated changes ### Related - `forgejo_admin/westside-app#109` — parent ticket (decomposed) - Sub-ticket 2: pal-e-services terraform updates - Sub-ticket 3: pal-e-deployments overlay updates - Sub-ticket 4: pal-e-platform monitoring probe update - `project-westside-basketball`

forgejo_admin commented

2026-03-28 19:20:03 +00:00

Author

Owner

Scope Review: READY

Review note: review-587-2026-03-28

All 11 template sections present. Traceability complete (story:WS-S26, arch:landing-site). File targets verified -- API-only operation, no code changes. Acceptance criteria testable. Blockers #534 and #529 are both in done. Well under 5-minute rule.

Minor cosmetic note: blocked-by:ws-534 and blocked-by:ws-529 labels on the board item could be cleaned up since both blockers are done.

## Scope Review: READY Review note: `review-587-2026-03-28` All 11 template sections present. Traceability complete (story:WS-S26, arch:landing-site). File targets verified -- API-only operation, no code changes. Acceptance criteria testable. Blockers #534 and #529 are both in `done`. Well under 5-minute rule. Minor cosmetic note: `blocked-by:ws-534` and `blocked-by:ws-529` labels on the board item could be cleaned up since both blockers are done.

forgejo_admin commented

2026-03-28 19:22:24 +00:00

Author

Owner

Rename Complete

Executed PATCH /api/v1/repos/forgejo_admin/westside-app with {"name": "westside-landing"}.

Verification Results

Check	Result
Repo accessible as `forgejo_admin/westside-landing`	Confirmed
Old URL `forgejo_admin/westside-app` redirects (301)	Confirmed
Live site `westsidekingsandqueens.tail5b443a.ts.net` returns HTTP 200	Confirmed
Woodpecker webhook active (hook ID 86, uses forge ID 35)	Confirmed
Local remote (`~/westside-app`) updated to new URL	Done

Remaining Manual Verification

Push a no-op commit to westside-landing to confirm Woodpecker pipeline triggers under the new name

Notes

Woodpecker webhook uses the internal Forgejo repo ID (35), not the repo name, so it survives renames automatically.
Forgejo sets up a 301 redirect from the old name, so existing bookmarks/links continue to work.
No code changes were made -- this was purely an API rename operation.
Sub-tickets 2-4 from #109 can now proceed (they depend on this rename completing first).

## Rename Complete Executed `PATCH /api/v1/repos/forgejo_admin/westside-app` with `{"name": "westside-landing"}`. ### Verification Results | Check | Result | |-------|--------| | Repo accessible as `forgejo_admin/westside-landing` | Confirmed | | Old URL `forgejo_admin/westside-app` redirects (301) | Confirmed | | Live site `westsidekingsandqueens.tail5b443a.ts.net` returns HTTP 200 | Confirmed | | Woodpecker webhook active (hook ID 86, uses forge ID 35) | Confirmed | | Local remote (`~/westside-app`) updated to new URL | Done | ### Remaining Manual Verification - [ ] Push a no-op commit to `westside-landing` to confirm Woodpecker pipeline triggers under the new name ### Notes - Woodpecker webhook uses the internal Forgejo repo ID (35), not the repo name, so it survives renames automatically. - Forgejo sets up a 301 redirect from the old name, so existing bookmarks/links continue to work. - No code changes were made -- this was purely an API rename operation. - Sub-tickets 2-4 from #109 can now proceed (they depend on this rename completing first).