Metadata-API

Metadata API

Per-repo identity, governance, deployment, and build metadata.

Endpoints

Method	Endpoint	Auth	Description
GET	`/api/v1/repos/{owner}/{repo}/metadata`	Public	Get metadata settings
PUT	`/api/v1/repos/{owner}/{repo}/metadata`	Admin	Update metadata settings (merge semantics)

Request/Response

{
  "name": "MokoGitea",
  "org": "MokoConsulting",
  "description": "Moko fork of Gitea",
  "license_spdx": "GPL-3.0-or-later",
  "license_name": "GNU General Public License v3",
  "platform": "go",
  "standards_version": "05.01.00",
  "standards_source": "https://git.mokoconsulting.tech/MokoConsulting/MokoCLI",
  "language": "Go",
  "extension_type": "application",
  "entry_point": "./",
  "display_name": "Application - MokoGitea",
  "deploy_host": "git.mokoconsulting.tech",
  "deploy_port": "2918",
  "deploy_user": "mokoconsulting",
  "deploy_path": "/opt/gitea",
  "docker_image": "mokogitea",
  "docker_registry": "",
  "container_name": "mokogitea",
  "health_url": "https://git.mokoconsulting.tech"
}

Notes

GET is public -- no authentication required.
PUT uses merge semantics -- only provided fields are updated, others are preserved.
display_name is read-only -- computed server-side as {ExtensionType} - {Name}.
extension_type replaces the former package_type field (renamed in v1.27.0).
The endpoint was renamed from /manifest to /metadata in v1.27.0.
.mokogitea/manifest.xml file is no longer used. Metadata is managed exclusively via the API.

Printed from wiki · Metadata-API