Login
View Ticket
Login
Ticket Hash: 60c7babba4a1f15a9645191a77f8b6446395c27c
Title: External CI results (GitLab pipeline, GitHub Pages run) land on the merged ticket automatically
Status: Active Type: Feature_Request
Severity: Normal Priority: Medium
Subsystem: Resolution:
Last Modified: 2026-09-20 18:14:24
51.6 days ago
Created: 2026-09-20 13:52:33
51.8 days ago
Version Found In:
Description:
OCX-PLAN: role=work parent=8a1d64dcdf seq=6 complexity=medium design_input=none

Maintainer, 2026-09-20: 'not sure where to report: <GitLab job URL>'. A failed pipeline on the mirror has no path back into Fossil; the maintainer carries the link by hand. Accountability: the claim 'merged and green' must include the runners that actually run the code the mirror ships. Do: after a merge's export reaches the destinations, the daemon polls the public pipeline and workflow-run APIs for that commit (GitLab pipelines by sha; GitHub actions runs by head_sha; both read anonymously today) and adds one comment to the merged ticket per result (runner, status, job URL); a failure sets the ticket back to Review with the log's failing lines when the log is readable, and the console shows it under In flight. Configuration is the existing git-destination row plus a per-repo gitlab-project row; no secrets. Spec with recorded API fixtures. Tag the guard (Accountability).

User Comments:
added on 2026-09-20 18:14:24:
Scope note (fable, 2026-09-20): include GitHub commit statuses, not only workflow runs; Xcode Cloud reports Stone's build result as a commit status on embedconsult/stone, so the same poller closes Stone's loop.