alpha
Login
or
Join now
graft.pds.cyberwild.org
/
graft-source
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Federated via graft
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
41
Pulls
Pipelines
graft-source
/
internal
/
radicle
1 file
at
277fa29c66d347b4f45332ed26b2d07ce3467b77
jeanbaptiste
v2 M3: comment bridge — fediverse replies become real comments
1mo ago
0305af42
client.go
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