Clean up JME's GitHub webhooks

Since we’ve abandoned Slack, I think we should remove the Slack webhooks.

One of the Discord hooks is showing a 400 Error. Does anyone know how to fix it? If not, perhaps we should remove it also.

I don’t think we’ve 100% abandoned slack. That’s where I read the github updates as I like the look/format better than on discord.

1 Like

Alright, we’ll keep the slack webhooks. Does anyone know how to fix the Discord one that’s broken?

Discord has two incoming Webhooks:
651033 and 646671, so we have both: One per Channel.
I don’t know about the error

Edit: Indeed we didn’t get any reports in #github-builds anymore.
What I did was to make both channels read only because people started replying in there, but the webhook broke earlier: on 4.2.

I will try to fix it.

1 Like

Possibly related to this e-mail I receive every 3 days:

On February 11th, 2020 at 20:48 (UTC) your application (jMonkeyEngine Community Hub) used an access token (with the User-Agent Faraday v0.17.3) as part of a query parameter to access an endpoint through the GitHub API.

Please use the Authorization HTTP header instead as using the `access_token` query parameter is deprecated and will be removed July 1st, 2020.

Depending on your API usage, we'll be sending you this email reminder once every 3 days.

Visit for more information.

The GitHub Team

I’m pretty sure that’s related to the discourse github SSO login. It should disappear with a discourse update at some point I’d have thought.


I also wonder why the webhook for discord fails, I rechecked the information and it seemed okay.
Maybe I have to completely delete the webhook instead of only updating it.

Edit: I lied, the events are delivered again, so i think this webhook in particular is solved.

1 Like

I’ve stopped getting e-mail notices from GitHub, but the Discord hook is still getting HTTP error responses (400).

Last Webhook Push arrived roughly 24h ago, so I wonder how this happens…

Sorry, I should have said “one of the Discord hooks”.

Well, the other one arrived 2 hours ago.
So it’s “working”, but we can delete them and re-set them up if that means we’re getting 200s again.