Github pushes doesn't seem to always send the event to pipedream

It’s happened a couples in the last few months and I’ve found that if you have the first same word on the Github commit title, it’s more of a chance that it doesn’t send that event to Pipedream. But this time it didn’t at all and had different characters at the start. I did use a word that was used in the previous commit which I don’t know if that matters.

It doesn’t happen all that often but it’s a little annoying to debug this and manually resend it every time.
Currently using the Github “New Push” event. I don’t know if there’s an option to rescan the Github commits (from pipedream) and manually send it again but that would be useful.

Any help would be great.

Hi @ReaLadge

Thanks for raising this issue.

I believe you’re using the Github - New Commit trigger.

If that’s the case, I think the issue might be that the commit’s message is being used as the event ID instead of the commit sha.

Here’s the source code of the trigger: pipedream/new-commit.mjs at master · PipedreamHQ/pipedream · GitHub

The dedupe strategy is set to unique, so if the component is mistakenly emitting the commit message as the name, then yes redundant names would be treated as the same.

You can fork our repository and try fixing it yourself - or you can open up a bug report here: Sign in to GitHub · GitHub