I found an excellent tutorial here: https://dev.to/sensiolabs/how-to-use-the-new-symfony-maker-command-to-work-with-github-webhooks-2c8n

and here:

https://ngandu.hashnode.dev/sending-github-notifications-to-telegram-a-symfony-webhook-guide

Sounds good to me.

Can you give me some guidance on how to set this up as a bundle? I imagine in the GithubWebhookBundle.php there's a service that has a tag on it, and then the application that uses the bundle adds a RemoteEventConsumer?

To me, parsing GitHub webhook payloads into a RemoteEvent is not something that belongs in the core of Symfony. Our parsers in core bridges are all about parsing a subset of the webhook payload into a shared abstraction of mailer or notifier webhooks. GitHub webhooks don't make sense in those abstraction.

Writing a dedicated GitHub-specific webhook request parser exposing the full GitHub payload to write GitHub-specific webhook consumers is something that should be provided by a bundle out of core IMO (which would also allow it to make releases much more often, to react to changes in the GitHub webhooks to add new fields for instance).
That bundle can reuse all the infrastructure of symfony/webhook in the core. It will mostly need to implement the appropriate RequestParser and register it as a service that projects can use in the webhook routing (which can even be provided in a recipe): https://symfony.com/doc/current/webhook.html

Symfony's @carsonbot uses github webhooks so if git webhook abstraction would be integrated in core, it could be direct user of this

if it is in a bundle, it could also use the bundle. The fact that one of our tool has such need is not a sufficient argument to bring it in core.
A SDK for GitHub webhook payloads needs to adapt constantly to the evolution of GitHub. A 6-month release schedule is not adapted for it.

Perhaps it would be a good fit for https://github.com/KnpLabs/php-github-api

Just brainstorming: The bundle could provide a command line tool that registers the webhook on github.

bin/console github:register https://my-application  --event=issue.new --event=pull.request --event=release.new

(I'm making up these event names).

Thank you for this suggestion.
There has not been a lot of activity here for a while. Would you still like to see this feature?
Every feature is developed by the community.
Perhaps someone would like to try?
You can read how to contribute to get started.

Friendly reminder that this issue exists. If I don't hear anything I'll close this.

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!