graft-source/internal/sync/ at 0305af427439c3a3d3a3ffc6508fd8477ffaaffd · graft.pds.cyberwild.org/graft-source · Tangled

graft.pds.cyberwild.org / graft-source

0

Federated via graft

0

graft-source / internal / sync

4 files

at 0305af427439c3a3d3a3ffc6508fd8477ffaaffd

jeanbaptiste v2 M3: comment bridge — fediverse replies become real comments 1mo ago

Group dashboard activity by repo, not by sync pair Each repo pair now declares an optional series, grouping every side that mirrors the same underlying repository (its Forgejo instances and Radicle node) under one row. The dashboard heatmap becomes one event per cell (never aggregated behind a single tooltip) inside a collapsible group per repo, expanding to one sub-row per actual mirrored server with its own link and its own events - instead of one ambiguous shared link. Also fixes git commit activity always linking to Forgejo regardless of which side the content actually landed on, so Radicle now shows up as a real destination instead of being invisible in the activity feed.

1 month ago

v2 M3: comment bridge — fediverse replies become real comments activity_log now records the forgejo_id/radicle_id of the issue/patch each entry is about, so a reply's inReplyTo can be resolved back to the exact item it's a comment on. Forgejo: CreateIssueComment (POST .../issues/{index}/comments — verified live, and confirmed the same endpoint takes PR comments too). Radicle: CommentIssue and CommentPatch via the rad CLI (verified against `rad issue/patch comment --help` on a live node first, rather than guessing the syntax — patch comments take a revision id, not the patch's own id, which the Patch/Revision struct now also carries). The inbox now handles Create{Note} whose inReplyTo points at one of our own Notes: strips the reply's HTML, prefixes it with the replying account's handle, and posts it as a comment on both the Forgejo and Radicle sides of whichever specific pair logged that entry. Verified live end-to-end without a real fediverse account, using one of graft's own already-published actors as the signed sender (its key never leaves the container — a small Go program run via `pct exec` reads it locally and signs the request there): the reply landed as a comment on both f2's issue and the Radicle issue, correctly attributed.

1 month ago

v2 M3: comment bridge — fediverse replies become real comments activity_log now records the forgejo_id/radicle_id of the issue/patch each entry is about, so a reply's inReplyTo can be resolved back to the exact item it's a comment on. Forgejo: CreateIssueComment (POST .../issues/{index}/comments — verified live, and confirmed the same endpoint takes PR comments too). Radicle: CommentIssue and CommentPatch via the rad CLI (verified against `rad issue/patch comment --help` on a live node first, rather than guessing the syntax — patch comments take a revision id, not the patch's own id, which the Patch/Revision struct now also carries). The inbox now handles Create{Note} whose inReplyTo points at one of our own Notes: strips the reply's HTML, prefixes it with the replying account's handle, and posts it as a comment on both the Forgejo and Radicle sides of whichever specific pair logged that entry. Verified live end-to-end without a real fediverse account, using one of graft's own already-published actors as the signed sender (its key never leaves the container — a small Go program run via `pct exec` reads it locally and signs the request there): the reply landed as a comment on both f2's issue and the Radicle issue, correctly attributed.

1 month ago

v2 M3: comment bridge — fediverse replies become real comments activity_log now records the forgejo_id/radicle_id of the issue/patch each entry is about, so a reply's inReplyTo can be resolved back to the exact item it's a comment on. Forgejo: CreateIssueComment (POST .../issues/{index}/comments — verified live, and confirmed the same endpoint takes PR comments too). Radicle: CommentIssue and CommentPatch via the rad CLI (verified against `rad issue/patch comment --help` on a live node first, rather than guessing the syntax — patch comments take a revision id, not the patch's own id, which the Patch/Revision struct now also carries). The inbox now handles Create{Note} whose inReplyTo points at one of our own Notes: strips the reply's HTML, prefixes it with the replying account's handle, and posts it as a comment on both the Forgejo and Radicle sides of whichever specific pair logged that entry. Verified live end-to-end without a real fediverse account, using one of graft's own already-published actors as the signed sender (its key never leaves the container — a small Go program run via `pct exec` reads it locally and signs the request there): the reply landed as a comment on both f2's issue and the Radicle issue, correctly attributed.

1 month ago