-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backfeed for github status changes #833
Comments
I'd love this too! sadly there's no comprehensive way to get all events on all issues that involve you. i can get a few beyond comments, best effort, but only a few, and that subset isn't entirely predictable. background: https://brid.gy/about#GitHub+responses, #333 (comment) i can definitely consider supporting the events that come back from the notifications API though! i worry a bit that the subset it includes will generate more confusion than it's worth, but maybe that's overthinking it. |
here's the subset in the notifications API, ie that we can reasonably get: https://developer.github.com/v3/activity/notifications/#notification-reasons
of those, next steps: figure out mf2 for those, and then see some indie example posts in the wild. feel free to help with either or both! |
This is actually a blocker for me |
understood! which status changes above specifically are blocking you? and as mentioned here and in #915, one big thing we're waiting on here is to see example posts in the wild, with concrete mf2, for these kinds of status changes in the wild. please do take the lead and post some of those! (also, as usual, PRs are welcome! these should definitely be straightforward to implement in granary. i'm happy to help! https://granary.readthedocs.io/en/stable/#development is a great place to start.) |
The issue is I want to own the experience of issue tracking... so I can't show open issues I've participated in on my website and go through them. |
snarfed/bridgy – feature request: backfeed for status changes
I would like bridgy to backfeed status changes so that POSSE’d issues can capture the full lifecycle of an issue.
Looks like there are tons of events: https://developer.github.com/v3/issues/events/
The issue was closed by the actor. When the commit_id is present, it identifies the commit that closed the issue using “closes / fixes #NN” syntax.
The issue was reopened by the actor.
The issue was assigned to the actor.
The actor was unassigned from the issue.
The issue title was changed.
(Originally published at: https://crw.moe/b/WF)
The text was updated successfully, but these errors were encountered: