Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Web Console: Gitea issue and PR linkage console (Phase 3) #645

New Issue
Open
opened 2026-07-10 14:41:09 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-10 14:41:09 -05:00
Owner
Copy Link
Copy Source

Problem statement

Operators need a console surface that shows Gitea issue↔PR linkage, handoff comments, labels, and controller state without becoming a full Gitea replacement editor.

User and operational impact

Lost context between issues/PRs; hard to see which PR closes which issue or latest canonical handoff.

Scope

  • Read-only linkage browser: issue → related PRs, PR → issue, labels, latest canonical state comment summary, timeline deep-link (#637).
  • Deep links to Gitea web UI (reveal endpoints only when allowed).
  • Optional filters by project/registry.

Explicit non-goals

  • No full issue/PR editor.
  • No browser review/merge.
  • No duplicate of Gitea search product.

Required implementation investigation

Queue loaders, Gitea list/view APIs, #429, #637, #640, #631, canonical comment modules.

Proposed architecture or implementation direction

Server-side Gitea reads via existing MCP/auth helpers; linkage DTO; HTML table + detail.

Security and workflow-safety requirements

Use server credentials only; redact; RBAC for which projects visible.

Acceptance criteria

  1. Issue/PR linkage visible for selected project/repo.
  2. Latest handoff summary when present.
  3. External link to Gitea when permitted.
  4. Tests with mocked Gitea payloads.
  5. Docs.

Required tests

Linkage resolution unit tests; view tests.

Observability and audit requirements

Read-only access logged if required by #633.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement Gitea linkage console view
NEXT_PROMPT: Author linkage view; PR; stop

Required final evidence

PR with view, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement Operators need a console surface that shows **Gitea issue↔PR linkage**, handoff comments, labels, and controller state without becoming a full Gitea replacement editor. ## User and operational impact Lost context between issues/PRs; hard to see which PR closes which issue or latest canonical handoff. ## Scope * Read-only linkage browser: issue → related PRs, PR → issue, labels, latest canonical state comment summary, timeline deep-link (#637). * Deep links to Gitea web UI (reveal endpoints only when allowed). * Optional filters by project/registry. ## Explicit non-goals * No full issue/PR editor. * No browser review/merge. * No duplicate of Gitea search product. ## Required implementation investigation Queue loaders, Gitea list/view APIs, #429, #637, #640, #631, canonical comment modules. ## Proposed architecture or implementation direction Server-side Gitea reads via existing MCP/auth helpers; linkage DTO; HTML table + detail. ## Security and workflow-safety requirements Use server credentials only; redact; RBAC for which projects visible. ## Acceptance criteria 1. Issue/PR linkage visible for selected project/repo. 2. Latest handoff summary when present. 3. External link to Gitea when permitted. 4. Tests with mocked Gitea payloads. 5. Docs. ## Required tests Linkage resolution unit tests; view tests. ## Observability and audit requirements Read-only access logged if required by #633. ## Dependencies and linkage * Parent: #631 · Soft-depends: #637, #640, #635 · Related: #626 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement Gitea linkage console view NEXT_PROMPT: Author linkage view; PR; stop ``` ## Required final evidence PR with view, tests, docs. ## Required final response and handoff expectations Brief PR → reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboard labels 2026-07-10 14:41:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels dashboard status:ready type:feature workflow-hardening
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#645