Add Woodpecker CI pipeline + ruff config + Forgejo PyPI publishing #1

New issue

Closed

opened 2026-03-01 17:12:29 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

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

Contributor

Plan

plan-2026-03-01-forgejo-pypi-migration — Phase 1

Repo

forgejo-mcp — the repo where the code change happens

User Story

As a platform developer
I need forgejo-mcp to have a Woodpecker CI pipeline that lints, tests (if applicable), builds, and publishes to Forgejo's private PyPI registry
So that the package is no longer leaked to public pypi.org and follows the standard CI pattern

Acceptance Criteria

When I push to main on forgejo-mcp
Then Woodpecker runs lint (ruff), tests (if present), and publishes the package to Forgejo PyPI
When I open a PR
Then Woodpecker runs lint and tests (no publish)

Additional Information

Reference implementation: woodpecker-sdk .woodpecker.yml (PR #6, merged after 3 QA rounds).

FastMCP server with 11 tools. Check if this repo has tests — include test step if yes, skip if no.

Global Woodpecker secrets already configured: forgejo_publish_user, forgejo_publish_token, forgejo_pypi_url.

Repo may need activating in Woodpecker.

Ruff config: py310, line-length 120, select E/F/W/I (matches platform standard).

Checklist

PR opened with related notes
Tests cover the acceptance criteria
Docs updated if needed

project-claude-config — parent project
plan-2026-03-01-forgejo-pypi-migration — the migration plan
plan-2026-02-28-woodpecker-sdk-mcp — reference implementation

### Plan `plan-2026-03-01-forgejo-pypi-migration` — Phase 1 ### Repo `forgejo-mcp` — the repo where the code change happens ### User Story As a platform developer I need forgejo-mcp to have a Woodpecker CI pipeline that lints, tests (if applicable), builds, and publishes to Forgejo's private PyPI registry So that the package is no longer leaked to public pypi.org and follows the standard CI pattern ### Acceptance Criteria When I push to main on forgejo-mcp Then Woodpecker runs lint (ruff), tests (if present), and publishes the package to Forgejo PyPI When I open a PR Then Woodpecker runs lint and tests (no publish) ### Additional Information Reference implementation: `woodpecker-sdk` `.woodpecker.yml` (PR #6, merged after 3 QA rounds). FastMCP server with 11 tools. Check if this repo has tests — include test step if yes, skip if no. Global Woodpecker secrets already configured: `forgejo_publish_user`, `forgejo_publish_token`, `forgejo_pypi_url`. Repo may need activating in Woodpecker. Ruff config: py310, line-length 120, select E/F/W/I (matches platform standard). ### Checklist - [ ] PR opened with related notes - [ ] Tests cover the acceptance criteria - [ ] Docs updated if needed ### Related - `project-claude-config` — parent project - `plan-2026-03-01-forgejo-pypi-migration` — the migration plan - `plan-2026-02-28-woodpecker-sdk-mcp` — reference implementation