4 Commits

Include renames

Author	SHA1	Message	Date
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
mathiasandmathias	3648373333	fix: merge repo_update — add archived+template, keep default_branch+confirm from main	2026-05-16 23:54:16 +02:00
mathias	eeefc626ed	feat(repo_update): tool for archiving + metadata patches ... Adds a repo_update tool exposing PATCH /api/v1/repos/{owner}/{name} with optional pointer fields (archived, description, private, website, template). Only fields set by the caller are sent on the wire, so the server patches exactly what was asked for. Originally needed to archive ingestion-svc cleanly instead of leaving a README tombstone, and to flip template-go-{agent,web} to template=true so create_project_from_template stops failing the "is not marked as template" guard. Wire-level enforcement of "at least one field" returns ErrValidation before any network call, preventing no-op PATCHes. private=false (making a repo public) is allowed but flagged in the tool description with a "verify intent before calling" warning. The earlier issue draft suggested an ntfy confirmation hook for that path — out of scope for this PR; the warning string is the minimum that fits inside the tool surface today. Wires NewRepoUpdate into cmd/gitea-mcp/main.go alongside the rest of the repo_* family. Closes #12	2026-05-16 23:54:16 +02:00
mathias	e2da495581	feat(tools): add repo_create, repo_update, repo_mirror_push (#12, #13, #16) ... repo_create: POST /user/repos or /orgs/{org}/repos, is_org flag routes repo_update: PATCH /repos/{owner}/{repo}, confirm required when private=false repo_mirror_push: add/list/delete push mirrors, password never returned	2026-05-15 10:14:18 +02:00