chore: remove per-repo clone URL override from .woodpecker.yml #39

New issue

Closed

opened 2026-03-14 22:24:41 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-14 22:24:41 +00:00

Owner

Lineage

todo-remove-clone-url-overrides (no plan ancestry)

Repo

forgejo_admin/pal-e-docs-mcp

User Story

As a platform operator
I want per-repo clone overrides removed from Woodpecker configs
So that clone behavior is managed centrally via WOODPECKER_FORGEJO_CLONE_URL

Context

PR #56 on pal-e-platform set WOODPECKER_FORGEJO_CLONE_URL globally. Per-repo clone overrides in .woodpecker.yml are now redundant. This override was originally added in pal-e-docs-mcp PR #15 to work around a TLS issue that has since been resolved.

File Targets

Files the agent should modify:

.woodpecker.yml — remove the clone: section (lines 1-5)

Files the agent should NOT touch:

The publish step referencing forgejo-http.forgejo.svc.cluster.local for PyPI — that's the Forgejo package registry URL, not a clone URL
Any other pipeline steps

Acceptance Criteria

The clone: section (lines 1-5) is removed from .woodpecker.yml
All other pipeline config remains unchanged
Pipeline passes on PR

Test Expectations

Woodpecker pipeline triggers and clone step uses global WOODPECKER_FORGEJO_CLONE_URL
Run command: N/A — verified by CI pipeline on PR

Constraints

Only remove the clone: block — do not modify any other pipeline configuration
The publish step has a FORGEJO_PYPI_URL that also uses forgejo-http.forgejo.svc.cluster.local — do NOT remove that, it's the package registry URL not a clone URL
Keep blank line separation between remaining top-level keys

Checklist

PR opened
No unrelated changes

todo-remove-clone-url-overrides — parent TODO
pal-e-platform PR #56 — set global clone URL

### Lineage `todo-remove-clone-url-overrides` (no plan ancestry) ### Repo `forgejo_admin/pal-e-docs-mcp` ### User Story As a platform operator I want per-repo clone overrides removed from Woodpecker configs So that clone behavior is managed centrally via WOODPECKER_FORGEJO_CLONE_URL ### Context PR #56 on pal-e-platform set WOODPECKER_FORGEJO_CLONE_URL globally. Per-repo clone overrides in .woodpecker.yml are now redundant. This override was originally added in pal-e-docs-mcp PR #15 to work around a TLS issue that has since been resolved. ### File Targets Files the agent should modify: - `.woodpecker.yml` — remove the `clone:` section (lines 1-5) Files the agent should NOT touch: - The `publish` step referencing `forgejo-http.forgejo.svc.cluster.local` for PyPI — that's the Forgejo package registry URL, not a clone URL - Any other pipeline steps ### Acceptance Criteria - [ ] The `clone:` section (lines 1-5) is removed from `.woodpecker.yml` - [ ] All other pipeline config remains unchanged - [ ] Pipeline passes on PR ### Test Expectations - [ ] Woodpecker pipeline triggers and clone step uses global WOODPECKER_FORGEJO_CLONE_URL - Run command: N/A — verified by CI pipeline on PR ### Constraints - Only remove the `clone:` block — do not modify any other pipeline configuration - The `publish` step has a `FORGEJO_PYPI_URL` that also uses `forgejo-http.forgejo.svc.cluster.local` — do NOT remove that, it's the package registry URL not a clone URL - Keep blank line separation between remaining top-level keys ### Checklist - [ ] PR opened - [ ] No unrelated changes ### Related - `todo-remove-clone-url-overrides` — parent TODO - pal-e-platform PR #56 — set global clone URL