This GitHub issue has 22 comments

[zaiste]

This GitHub issue is automated 🤖 using GraphQL. There is a GraphQL subscription that listens for changes on this issue and a GraphQL mutation that changes the title once a change occurs. Those two GraphQL statements are chained together and hosted by OneGraph. As a bonus, the chain also contains a GraphQL query for checking the GitHub's API rate limits.

Just comment below to see the magic. 👇

[zaiste]

Test

[sgrove]

The limits of my programming language mean the limits of my circle of friends.

[zaiste]

Another comment. It all works thanks to OneGraph

[sgrove]

Whereof one cannot speak, thereof one must make bold proclamations.

[zaiste]

I couldn't get live reactions in OneGraph :)

[zaiste]

test

[zaiste]

test

[zaiste]

test

[zaiste]

test

[zaiste]

test

[dwwoelfel]

I couldn't get live reactions in OneGraph :)

No subscriptions for reactions unfortunately. You could set up another query chain with the poll subscription to update the reaction count, though. It accepts any query and will run it on a schedule.

[dwwoelfel]

It might be interesting to compare this with github actions. I tried it with essay.dev to post a message on the issue directing you to the blog post (e.g. OneGraph/essay.dev#33 (comment)). It was a bit too slow for my use case, maybe 15 seconds. I was worried the user would have left the page before the comment posted.

[nivertech]

Show me the m̶o̶n̶e̶y̶ magic!

[nivertech]

This GitHub issue has 14 comments

[YitziG]

This is not a comment.

[jsnoyes]

Hey, everybody. Just got back from my hypnotherapist. He said I’d turn into a chicken if I hear the number that comes after 15. Luckily I haven’t come across that yet.

[jsnoyes]

Cluck

[jsnoyes]

Whoa what just happened? I blacked out there for a second.

[lukeberry99]

This is pretty sick.

[btwiuse]

btw i use arch

[1vnt]

🍪

[1vnt]

nice