Publish issue/PR reaction events somewhere

[chadwhitacre]

@jonesphillip wants to know when someone upvotes an issue, so he can follow up with them. 👍

Maybe this is a Slack tie-in? Routed based on Team: label assignments to one #channel or another?

[BYK]

I'll take this on and do some investigation today.

[BYK]

So turns out GitHub doesn't have a webhook for reactions but they do have an API for them.

Proposed solution: create a daily ETL job that scrapes all open issues and creates a table with reactions count and Team: labels information. Feed this into Looker and create a dashboard that is shared weekly.

@chadwhitacre @jonesphillip thoughts?

[chadwhitacre]

Sounds like this write-up, maybe some ideas in there?

Should we try to use github_events for this? We'd need to add a team field, and I'd hate for that to be a mutable string, better to have an id ... get the Notion DB API idea going first? I guess that is relevant whether we use github_events or a new table.

field	value
type	issues
action	count-upvotes
username
user_id
repository
object_id
created_at
updated_at
target_id	54 ← overload this? doesn't feel great
target_name
target_type
webhook_source
user_type
team_id	79676C8E-2F83-4FE8-BBD0-1A91FA2D2000

[chadwhitacre]

GitHub doesn't have a webhook for reactions

P.S. I upvoted that and also filed a support ticket to upvote internally. So meta. :P

[chadwhitacre]

Possibly related? https://sourcekarma.vercel.app/

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[chadwhitacre]

I still like this as a future iteration on our GitHub notifications, somewhere after #89.