feat: issue metadata API + org wiki tab #590

Open
jmiller wants to merge 2 commits from chore/mcp-cleanup into main
Owner

Summary

  • Issue Status/Priority/Type API: Exposes org-level issue metadata through the REST API and MCP tools. Issues now include status_id, priority_id, type_id with resolved names. New org endpoints list available definitions. Create/edit issue endpoints accept metadata IDs.
  • Org Wiki Tab: Inline wiki on the org page using convention repos (wiki for public, wiki-private for members-only). Renders markdown with the same pipeline as repo wikis. Public/private view dropdown matches the org profile README selector UX.
  • External Wiki Support: Org settings option to link to an outside wiki URL instead of using internal repos. Wiki tab links out with external icon when configured.
  • 5 new MCP tools: gitea_org_issue_statuses_list, gitea_org_issue_priorities_list, gitea_org_issue_types_list, gitea_issue_set_status, gitea_issue_set_priority

Test plan

  • GET /api/v1/orgs/MokoConsulting/issue-statuses returns status definitions
  • GET /api/v1/orgs/MokoConsulting/issue-priorities returns priority definitions
  • GET /api/v1/orgs/MokoConsulting/issue-types returns type definitions
  • PATCH /api/v1/repos/{owner}/{repo}/issues/{n} with status_id updates issue
  • GET /api/v1/repos/{owner}/{repo}/issues/{n} includes status_name, priority_name, type_name
  • Create wiki repo under org, push Home.md -> Wiki tab appears on org page
  • Create wiki-private repo -> public/private dropdown appears for members
  • Set wiki mode to external in org settings -> tab links to external URL
  • Migration 354 adds wiki_mode/wiki_url columns without errors
## Summary - **Issue Status/Priority/Type API**: Exposes org-level issue metadata through the REST API and MCP tools. Issues now include `status_id`, `priority_id`, `type_id` with resolved names. New org endpoints list available definitions. Create/edit issue endpoints accept metadata IDs. - **Org Wiki Tab**: Inline wiki on the org page using convention repos (`wiki` for public, `wiki-private` for members-only). Renders markdown with the same pipeline as repo wikis. Public/private view dropdown matches the org profile README selector UX. - **External Wiki Support**: Org settings option to link to an outside wiki URL instead of using internal repos. Wiki tab links out with external icon when configured. - **5 new MCP tools**: `gitea_org_issue_statuses_list`, `gitea_org_issue_priorities_list`, `gitea_org_issue_types_list`, `gitea_issue_set_status`, `gitea_issue_set_priority` ## Test plan - [ ] `GET /api/v1/orgs/MokoConsulting/issue-statuses` returns status definitions - [ ] `GET /api/v1/orgs/MokoConsulting/issue-priorities` returns priority definitions - [ ] `GET /api/v1/orgs/MokoConsulting/issue-types` returns type definitions - [ ] `PATCH /api/v1/repos/{owner}/{repo}/issues/{n}` with `status_id` updates issue - [ ] `GET /api/v1/repos/{owner}/{repo}/issues/{n}` includes `status_name`, `priority_name`, `type_name` - [ ] Create `wiki` repo under org, push `Home.md` -> Wiki tab appears on org page - [ ] Create `wiki-private` repo -> public/private dropdown appears for members - [ ] Set wiki mode to external in org settings -> tab links to external URL - [ ] Migration 354 adds `wiki_mode`/`wiki_url` columns without errors
jmiller added 2 commits 2026-06-08 10:23:26 +00:00
chore: update mcp-mokogitea-api submodule with CI fixes
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Generic: Repo Health / Repository health (push) Blocked by required conditions
Generic: Repo Health / Report Issues (push) Blocked by required conditions
Generic: Repo Health / Site Health (push) Has been skipped
Generic: Repo Health / Access control (push) Successful in 3s
6070f7dbd4
feat: issue metadata API + org wiki tab with internal/external mode
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Generic: Repo Health / Repository health (push) Blocked by required conditions
Generic: Repo Health / Report Issues (push) Blocked by required conditions
Generic: Repo Health / Site Health (push) Has been skipped
Generic: Repo Health / Access control (push) Successful in 2s
Generic: Project CI / Tests (pull_request) Blocked by required conditions
Generic: Repo Health / Scripts governance (pull_request) Blocked by required conditions
Generic: Repo Health / Repository health (pull_request) Blocked by required conditions
Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped
Generic: Repo Health / Report Issues (pull_request) Blocked by required conditions
Generic: Repo Health / Site Health (pull_request) Has been skipped
Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Generic: Repo Health / Access control (pull_request) Successful in 1s
Universal: Build & Release / Promote to RC (pull_request) Failing after 6s
Generic: Project CI / Lint & Validate (pull_request) Successful in 27s
PR RC Release / Build RC Release (pull_request) Failing after 36s
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 37s
b762c94a25
Issue Status/Priority/Type API:
- Expose status_id, priority_id, type_id (with resolved names) on Issue API struct
- New endpoints: GET /orgs/{org}/issue-statuses, /issue-priorities, /issue-types
- CreateIssue and EditIssue handlers accept status_id, priority_id, type_id
- MCP tools: 5 new tools + updated create/update with metadata params

Org Wiki Tab:
- Convention repos: wiki (public) and wiki-private (members-only)
- Inline wiki rendering with markdown pipeline, sidebar, footer, page list
- Public/private view dropdown (same UX as org profile README selector)
- External wiki mode: link to outside URL from wiki tab
- Wiki mode setting in org settings (internal vs external with URL field)
- Migration 354: add wiki_mode and wiki_url to user table
Some required checks failed
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Generic: Repo Health / Repository health (push) Blocked by required conditions
Generic: Repo Health / Report Issues (push) Blocked by required conditions
Generic: Repo Health / Site Health (push) Has been skipped
Generic: Repo Health / Access control (push) Successful in 2s
Generic: Project CI / Tests (pull_request) Blocked by required conditions
Generic: Repo Health / Scripts governance (pull_request) Blocked by required conditions
Generic: Repo Health / Repository health (pull_request) Blocked by required conditions
Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped
Generic: Repo Health / Report Issues (pull_request) Blocked by required conditions
Generic: Repo Health / Site Health (pull_request) Has been skipped
Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Generic: Repo Health / Access control (pull_request) Successful in 1s
Universal: Build & Release / Promote to RC (pull_request) Failing after 6s
Generic: Project CI / Lint & Validate (pull_request) Successful in 27s
PR RC Release / Build RC Release (pull_request) Failing after 36s
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 37s
This pull request has changes conflicting with the target branch.
  • CHANGELOG.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin chore/mcp-cleanup:chore/mcp-cleanup
git checkout chore/mcp-cleanup
Sign in to join this conversation.