feat(settings): add manifest.xml settings tab in repo settings #335

New Issue

2026-05-31T14:34:55Z

jmiller commented

2026-05-31 14:34:55 +00:00

Summary

Add a new "Manifest" tab in repository settings that exposes the fields from .mokogitea/manifest.xml as an editable form. These settings drive releases and update stream information.

Context

The moko-platform manifest (.mokogitea/manifest.xml) defines project identity, governance, and build configuration. Currently this file must be edited manually. The settings should be editable from the repo settings UI and used to populate:

Release display names (the <name> shown in update feeds)
Update descriptions (per-stream descriptions like "MokoGitea stable build")
Version information displayed in releases
Update stream metadata (element name, type, client, maintainer info)

Manifest Fields to Expose

From .mokogitea/manifest.xml:

Identity Section

name — Display name of the project
org — Organization
description — Project description (used in update feed descriptions)
version — Current version
license — SPDX identifier + human-readable name

Governance Section

platform — Platform type (go, node, etc.)
standards-version — moko-platform standards version
standards-source — URL to standards repo

Build Section

language — Primary language
package-type — application, library, etc.
entry-point — Build entry point

How These Settings Are Used

The manifest fields feed into updates.xml generation for releases:

identity.name -> <name> in each update entry
identity.description -> base for stream-specific descriptions (e.g., "{name} {stream} build.")
identity.version -> <version> in update entries
build.package-type -> <type> in update entries
Maintainer info from org settings -> <maintainer> and <maintainerurl>

Implementation Notes

Add as a new tab in repo settings (alongside Branches, Tags, etc.)
Schema reference: https://code.mokoconsulting.tech/MokoConsulting/moko-platform
Should validate against the moko-platform schema
Store in the manifest file itself (commit changes to repo on save)
Consider read-only display for governance fields (set by org standards)

## Summary Add a new "Manifest" tab in repository settings that exposes the fields from `.mokogitea/manifest.xml` as an editable form. These settings drive releases and update stream information. ## Context The moko-platform manifest (`.mokogitea/manifest.xml`) defines project identity, governance, and build configuration. Currently this file must be edited manually. The settings should be editable from the repo settings UI and used to populate: - **Release display names** (the `<name>` shown in update feeds) - **Update descriptions** (per-stream descriptions like "MokoGitea stable build") - **Version information** displayed in releases - **Update stream metadata** (element name, type, client, maintainer info) ## Manifest Fields to Expose From `.mokogitea/manifest.xml`: ### Identity Section - `name` — Display name of the project - `org` — Organization - `description` — Project description (used in update feed descriptions) - `version` — Current version - `license` — SPDX identifier + human-readable name ### Governance Section - `platform` — Platform type (go, node, etc.) - `standards-version` — moko-platform standards version - `standards-source` — URL to standards repo ### Build Section - `language` — Primary language - `package-type` — application, library, etc. - `entry-point` — Build entry point ## How These Settings Are Used The manifest fields feed into `updates.xml` generation for releases: - `identity.name` -> `<name>` in each update entry - `identity.description` -> base for stream-specific descriptions (e.g., "{name} {stream} build.") - `identity.version` -> `<version>` in update entries - `build.package-type` -> `<type>` in update entries - Maintainer info from org settings -> `<maintainer>` and `<maintainerurl>` ## Implementation Notes - Add as a new tab in repo settings (alongside Branches, Tags, etc.) - Schema reference: `https://code.mokoconsulting.tech/MokoConsulting/moko-platform` - Should validate against the moko-platform schema - Store in the manifest file itself (commit changes to repo on save) - Consider read-only display for governance fields (set by org standards) ## Related - Update stream config: `models/licenses/update_stream_config.go` - Current update feed: `updates.xml` - Manifest schema: moko-platform repo --- *Created by Claude Opus 4.6*

jmiller added the tech-debt label 2026-05-31 14:34:55 +00:00

jmiller closed this issue

2026-06-02 11:20:47 +00:00

jmiller referenced this issue from a commit

2026-06-02 11:47:41 +00:00

feat(settings): add extension metadata to repo settings (#335)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#335