Rename pal-e-docs-app to pal-e-production [DECOMPOSED]

### Type Feature ### Lineage Convention update — pipeline naming: playground → production → store. ### Repo `forgejo_admin/pal-e-docs-app` (parent — decomposes across 4 repos) ### User Story As a superadmin, I want the frontend repo named `pal-e-production` so that the pipeline stages are explicit: playground → production → store. ### Context Current naming (`pal-e-docs-app`) is ambiguous — "app" could mean anything. Renaming to `pal-e-production` makes the pipeline stage clear. This follows the same pattern as the westside-app → westside-landing rename (#109). ### File Targets No code changes in this parent issue — it decomposes into sub-tickets. ### Acceptance Criteria - [ ] All sub-tickets completed and validated - [ ] No broken CI pipelines - [ ] ArgoCD still deploys correctly - [ ] Naming convention docs updated ### Test Expectations - [ ] All sub-tickets pass individually - [ ] End-to-end: push to renamed repo triggers CI, builds image, ArgoCD deploys ### Constraints - Sub-ticket 1 (Forgejo rename) must complete FIRST — all others depend on it - Woodpecker CI auto-follows the Forgejo rename - Harbor image repo name may need updating ### Checklist - [ ] Sub-ticket 1: Forgejo repo rename (API call) - [ ] Sub-ticket 2: pal-e-services terraform refs - [ ] Sub-ticket 3: pal-e-deployments ArgoCD overlays - [ ] Sub-ticket 4: pal-e-platform monitoring probes - [ ] Convention docs updated ### Related - `project-pal-e-platform` - `westside-app#109` — prior art for this pattern

forgejo_admin commented

2026-03-29 19:59:34 +00:00

Contributor

Type

Feature

Lineage

Convention update — pipeline naming: playground → production → store.

Repo

forgejo_admin/pal-e-docs-app (parent — decomposes across 4 repos)

User Story

As a superadmin, I want the frontend repo named pal-e-production so that the pipeline stages are explicit: playground → production → store.

Context

Current naming (pal-e-docs-app) is ambiguous — "app" could mean anything. Renaming to pal-e-production makes the pipeline stage clear. This follows the same pattern as the westside-app → westside-landing rename (#109).

File Targets

No code changes in this parent issue — it decomposes into sub-tickets.

Acceptance Criteria

All sub-tickets completed and validated
No broken CI pipelines
ArgoCD still deploys correctly
Naming convention docs updated

Test Expectations

All sub-tickets pass individually
End-to-end: push to renamed repo triggers CI, builds image, ArgoCD deploys

Constraints

Sub-ticket 1 (Forgejo rename) must complete FIRST — all others depend on it
Woodpecker CI auto-follows the Forgejo rename
Harbor image repo name may need updating

Checklist

Sub-ticket 1: Forgejo repo rename (API call)
Sub-ticket 2: pal-e-services terraform refs
Sub-ticket 3: pal-e-deployments ArgoCD overlays
Sub-ticket 4: pal-e-platform monitoring probes
Convention docs updated

project-pal-e-platform
westside-app#109 — prior art for this pattern

Commenting is not possible because the repository is archived.

Rows
Columns

Rename pal-e-docs-app to pal-e-production [DECOMPOSED] #97