4 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 4.8	64176fe6d7	fix(repo_mirror_push): resolve mirror credential from server env, not the payload (#49) ... The mirror credential no longer has to ride the tool-call payload (which is persisted to transcript → claudewatcher → brain → gitea history). Adds remote_password_env: the name of a server-side env var the tool resolves at call time, so the secret stays in the server process. An env name that resolves to empty errors loudly rather than silently sending an empty password. Raw remote_password still works but the schema/description now mark it DISCOURAGED. Tests: password resolved from the env var (never in output); unset env var → ErrValidation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-04 09:00:07 +02:00
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
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