Bug: Woodpecker CI not tracking renamed repo pal-e-production #99
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-app#99
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Type
Bug
Lineage
Discovered during pal-e-production#98 (Forgejo rename). Woodpecker didn't auto-follow.
Repo
forgejo_admin/pal-e-productionWhat Broke
After renaming
pal-e-docs-app→pal-e-productionvia Forgejo API, Woodpecker CI still references the old name internally (ID 18,forge_urlpoints to old name). The new repo name returns 404 from Woodpecker API. CI pipelines will not trigger on push.Repro Steps
forgejo_admin/pal-e-productionmcp__woodpecker__get_repo("forgejo_admin/pal-e-production")→ 404Expected Behavior
Woodpecker should track the renamed repo and trigger pipelines on push.
Environment
Acceptance Criteria
forgejo_admin/pal-e-productionpal-e-docs-appreference removedRelated
pal-e-production#97— parent rename decompositionpal-e-production#98— Forgejo rename step