Files
GitHop/docs/gitea-hop-native.md
T
Hop fee4f6dd31 Add a secure repository Prompts review surface and prompt metadata API
Hop-State: A_06FN6MRSHG4B64ZV13086G8
Hop-Proposal: R_06FN6MQDE14FFNR65H1D28G
Hop-Task: T_06FN6J8ECE1Z9XQ5PQ3Z3D8
Hop-Attempt: AT_06FN6J8ECC1SC794JMZ0TF8
2026-07-11 15:36:22 -07:00

1.7 KiB

Hop-native Gitea semantics

HopWeb keeps Gitea's existing forge interface and adds a Hop-specific public home page, brand mark, and semantic vocabulary for collaboration elements.

Install

From the project root:

./deploy/gitea/install-hop-native.sh

Set ENV_FILE when the Compose environment is stored elsewhere:

ENV_FILE=/path/to/environment ./deploy/gitea/install-hop-native.sh

The installer copies the home page, brand mark, styles, and adapter into Gitea's persistent custom directory, sets the application name to Hop, restarts Gitea, and waits for a healthy response. Re-run it after editing an asset or replacing the Gitea volume.

Semantic mapping

Native route and behavior Hop label
Repository code Files
Prompts (Hop-native causal record)
Issues Tasks
Branches Attempts
Commits Checkpoints
Pull requests Proposals
Actions Evidence
Merge pull request Accept proposal

The adapter updates visible text, document titles, form placeholders, tooltips, and ARIA labels. It scopes replacements to Gitea navigation, headings, menus, breadcrumbs, labels, and buttons, so repository content and user-authored prose remain unchanged.

Repository home pages also receive a Hop workflow group in the existing Gitea sidebar. It uses Gitea's own classes, links, icons, and live counts.

Upgrade check

After changing the pinned Gitea version:

  1. run the installer;
  2. confirm Prompts, Tasks, Proposals, and Evidence in repository navigation;
  3. confirm Attempts and Checkpoints in the Files view;
  4. confirm proposal creation and acceptance labels;
  5. inspect browser console errors; and
  6. test a narrow viewport and keyboard navigation.