Issue and PR content are not social artifacts, they belong in the repo or at least its hosting instance. Likes and activity feed are the sort of thing that belongs in the social layer.
Yes, code is largely about communication as well - with others as well as our future selves. That doesn’t mean it’s a social media experience. There are lots of ways to communicate that aren’t that.
https://github.com/google/git-appraise
The idea is to use git-notes for issues & PRs, because git is already distributed by design and these elements of SDLC centralized our usage.
It does look like Tangled currently does those in a weird way, ties to the issue owner rather than repo - but here’s a proposal to fix: https://leaflet.pub/p/did%3Aplc%3Axasnlahkri4ewmbuzly2rlc5/3...
Doing some weird distributed join across all your committer’s PDSs seems a bit weird, and the semantics of cross-referencing issues seems gnarly in that world.
I think I’d be OK to model a PR as a tweet, it’s more owned by the sender. But issues seem like they should be owned by the repo for sure.