5 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 4.8	4c1f36f9eb	chore(rename): module gitea.d-ma.be → git.d-ma.be/mathias/gitea-mcp (#39) ... Gitea host renamed (infra ADR-0004); the mcp-chassis dep already migrated (3329ff3), so the sequencing gate is clear. `go mod edit -module` + bulk import rewrite across all .go files. gitea-mcp is a server binary (not an imported library), so no downstream consumers break. build + task check green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 22:48:26 +02:00
mathiasandClaude Opus 4.8	93c32edbb5	feat(tools): make repo the canonical repo-identifier arg; name now an alias (#38) ... Every caller (claude.ai connector, LLMs primed on gitea/GitHub) sends the repo identifier as `repo`, but the 33 per-repo identifier tools advertised `name`. The v0.2.8 shim aliased repo->name so it worked, yet the advertised inputSchema still said `name` — a misleading contract, with the shim load-bearing. - Flip all 33 identifier tools: schema property + required + struct field/tag from `name` to `repo`. A compliant `repo` caller now matches the struct directly; the shim is pure back-compat. - normalizeAliases is now bidirectional (name<->repo), so legacy `name` callers still resolve, and repo_create / create_project_from_template — whose `name` means "name of the NEW repo", not an existing-repo id — keep `name` and still accept `repo`. - `number`/`index` left as-is (out of scope; separate pre-existing quirk where pr_merge advertises `index` rather than `number`). - Tests: schema-canonical assertion + flipped alias round-trip (explicit `repo` wins over `name`). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 21:42:18 +02:00
mathiasandClaude Opus 4.8	4ebea7d023	fix(workflow_run_trigger): 204 dispatch is success; resolve run via listing (#41) ... Gitea's workflow_dispatch endpoint returns 204 No Content with no Location header. DispatchWorkflow required that header, so every successful dispatch errored with "missing Location header" and never yielded a run ID — making the tool unusable for CAD dispatch. - DispatchWorkflow now returns error-only; 204 = success, no Location needed. Body already carried ref+inputs; kept and covered by test. - Tool snapshots the newest existing workflow_dispatch run before dispatch, then polls ListWorkflowRuns after and returns the newest run with ID above that baseline (avoids returning a stale prior run). Falls back to an honest "dispatched, run not yet registered" result rather than failing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 21:12:45 +02:00
mathias	4274b48ea5	feat(gitea): default-branch lru cache ... Shared LRU avoids repeated Gitea calls for default-branch resolution; the simple stdlib map alternative would race on concurrent access without a mutex per entry, which is more code than the LRU.	2026-05-04 23:06:06 +02:00
mathias	ba172e3db8	feat(tools): workflow_run_trigger	2026-05-04 22:25:10 +02:00