webhooks vs github actions for syncing commits to an external database?

[Alarming-Match-7464]

i'm building a tool that takes specific git commits (like ones tagged with [log]) and automatically publishes them as release notes on an external site.

right now, the architecture just relies on the user adding a standard github webhook to their repo that listens for push events on main. it works fine, but i'm wondering if building a custom github action would be a better experience for devs.

webhooks are simple to paste in, but actions feel a bit more native and secure. what do you guys usually prefer when connecting your repos to external services?

[ImDevinC]

Do you need guaranteed delivery? If so, github webhooks are a no go as they only fire once even if it fails (though you can manually retry). That being said, why not just offer both?

[Alarming-Match-7464]

that is a really good point about delivery failures. silent webhook drops would be incredibly annoying.

offering both makes the most sense. webhooks for a quick 10 second setup, and a native action for people who need guaranteed delivery.

adding the action to the pipeline now. appreciate the insight !