Rename: Forgejo API rename pal-e-docs-app → pal-e-production #98

New issue

Closed

opened 2026-03-29 19:59:46 +00:00 by forgejo_admin · 1 comment

forgejo_admin commented

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

Contributor

Type

Feature

Lineage

Sub-ticket 1 of pal-e-docs-app#97 (rename decomposition). Must complete FIRST.

Repo

forgejo_admin/pal-e-docs-app

User Story

As a superadmin, I want the Forgejo repo renamed via API so that all downstream references can update.

Context

Forgejo API rename operation. Woodpecker CI webhook auto-follows. After rename, verify CI still triggers on push.

File Targets

No code changes — Forgejo API call only:

curl -X PATCH /api/v1/repos/forgejo_admin/pal-e-docs-app -d '{"name": "pal-e-production"}'

Acceptance Criteria

Repo accessible at forgejo_admin/pal-e-production
Old URL redirects or returns 404
Woodpecker CI repo still linked
Push to main still triggers pipeline

Test Expectations

curl the new repo URL — 200
Push a no-op commit — CI triggers

Constraints

BLOCKER for sub-tickets 2-4 — must complete first
Update local git remote after rename: git remote set-url origin <new-url>

Checklist

API rename executed
Woodpecker verified
Local remote updated

pal-e-docs-app#97 — parent decomposition

### Type Feature ### Lineage Sub-ticket 1 of `pal-e-docs-app#97` (rename decomposition). Must complete FIRST. ### Repo `forgejo_admin/pal-e-docs-app` ### User Story As a superadmin, I want the Forgejo repo renamed via API so that all downstream references can update. ### Context Forgejo API rename operation. Woodpecker CI webhook auto-follows. After rename, verify CI still triggers on push. ### File Targets No code changes — Forgejo API call only: ```bash curl -X PATCH /api/v1/repos/forgejo_admin/pal-e-docs-app -d '{"name": "pal-e-production"}' ``` ### Acceptance Criteria - [ ] Repo accessible at `forgejo_admin/pal-e-production` - [ ] Old URL redirects or returns 404 - [ ] Woodpecker CI repo still linked - [ ] Push to main still triggers pipeline ### Test Expectations - [ ] `curl` the new repo URL — 200 - [ ] Push a no-op commit — CI triggers ### Constraints - BLOCKER for sub-tickets 2-4 — must complete first - Update local git remote after rename: `git remote set-url origin <new-url>` ### Checklist - [ ] API rename executed - [ ] Woodpecker verified - [ ] Local remote updated ### Related - `pal-e-docs-app#97` — parent decomposition

forgejo_admin commented

2026-03-29 20:01:12 +00:00

Author

Contributor

Forgejo rename complete. Repo accessible at forgejo_admin/pal-e-production.

Local remote updated.

Blocker: Woodpecker CI still references old name (pal-e-docs-app, ID 18). Needs manual re-activation in Woodpecker UI. Also note: last 3 CI runs were already failing before rename.

Closing rename step — Woodpecker fix is a separate ops task.

**Forgejo rename complete.** Repo accessible at `forgejo_admin/pal-e-production`. Local remote updated. **Blocker:** Woodpecker CI still references old name (`pal-e-docs-app`, ID 18). Needs manual re-activation in Woodpecker UI. Also note: last 3 CI runs were already failing before rename. Closing rename step — Woodpecker fix is a separate ops task.