I was looking at aragonās discord and i like this channel they have where they see all pull requests, itās really easy to do, but you have to have permissions on github i think.
and hereās a pic of how it looks
I was looking at aragonās discord and i like this channel they have where they see all pull requests, itās really easy to do, but you have to have permissions on github i think.
Love it!
We should check on a couple thingsā¦
#1 We will eventually move to our own discord
#2 How easy is it to add new repos to the party
#3 We might want to have 2 channels, one for all the github activity, and another for Project Management, as we are using this repo to organize work in general: https://github.com/TECommons/Coordinationā¦
Seems like there is no way to add a whole github account, so it is manual, repo by repo, adding a webhook to each repo with an endpoint to the discord channel
#1 Moving to our own discord
Separating from the general token engineering community? Personally Iām hesitant on that, I love the comprehensive community that is TE, I think itās so cool that the commons and the academy are in one place. Is there a forum post or other resource dedicated to this discussion?
Yeah I didnāt understand that, I was thinking since discord is open source maybe @Griff wanted to program āour own discordā ^^
I donāt think Discord is open source.
yeah, they love open-source but they are not open source, my bad
Thatās true for the outgoing webhook from Github, however there are indeed other ways to integrate something like this to connect Github and Discord. (these are all triggers)
A relatively straight-forward one would be a github action that runs on issue
, pull_request
(which are all events thrown by github, and can be set as triggers on the action) and push
and sends a message to github via a webhook.
This should be easily configurable by adding one file in the github repo(in the .github/workflows
folder)
#1 Welp we moved ; )
#2 If we set up a github action to do this, weād only need to like add one YAML
file in the .github/workflows
folder, and that should do it : ) (Other methods might be more or less complex)
#3 We could maybe set up two channels. Having one channel logging all the coordination
repo stuff would be really cool. It would be like a ākeep track of zenhub, while using discordā channel
Iām on board with trying this out!
@KrisJ has looked at zappier as a solution to have github notifications (mentions specifically) sent to Discord DMs though it was too pricey to implement. But this could be really useful too.
The notifications from mentions would be slightly trickier to implementā¦ but should be do-able
I set up the channel to keep track of the coordination
repo. (It doesnāt track mentions, but just sends event updates via a Webhook whenever something happens in the coordination
repo).
For tracking the mentions etc. we might need to customise and make our own integration on github-actions.
AMAZING!! That is great!