Make forge fedora-messaging better #569

New issue

Open

opened 2026-05-12 10:09:00 +00:00 by humaton · 2 comments

humaton commented

2026-05-12 10:09:00 +00:00

Owner

Summary

Emit messages for all the repository/organization event messages to fedora-messaging

Details

No response

### Summary Emit messages for all the repository/organization event messages to fedora-messaging ### Details _No response_

humaton added the

labels

2026-05-12 10:09:00 +00:00

lecris commented

2026-05-12 10:20:46 +00:00

One option would be to mirror the event types that forgejo provides

Either the overall ones repository/issue/pull_request/action, or the more granular ones e.g. repository.create.

Keeping all of the schemas in sync might be a maintenance chore, and I could not find a reference for where (or even if) the webhook schema is defined in the source. If we make the schema be a generic object and say it's not fedora-messaging place to define it, then that could also simplify things.

One option would be to mirror the event types that forgejo provides ![image](/attachments/71622e53-1c21-4e7d-8232-94c2efcd3124) Either the overall ones `repository`/`issue`/`pull_request`/`action`, or the more granular ones e.g. `repository.create`. Keeping all of the schemas in sync might be a maintenance chore, and I could not find a reference for where (or even if) the webhook schema is defined in the source. If we make the schema be a generic `object` and say it's not fedora-messaging place to define it, then that could also simplify things.

image.png

123 KiB

t0xic0der commented

2026-05-13 06:09:21 +00:00

Member

@lecris we can add more event triggers, and the schema package can be found here. As this is a different package entirely for the schema, I do not think this would be a difficult thing to do, but we need to be sure that there is indeed a good case for request granularity. I do not want to create sub objects per repository or organization, as that breaks the established format that we have so far only for the sake of easier management. The dashboard anyway clearly describes the webhook event type as well on the listing.

@lecris we can add more event triggers, and the schema package can be found [here](https://github.com/fedora-infra/webhook-to-fedora-messaging-messages). As this is a different package entirely for the schema, I do not think this would be a difficult thing to do, but we need to be sure that there is indeed a good case for request granularity. I do not want to create sub objects per repository or organization, as that breaks the established format that we have so far only for the sake of easier management. The dashboard anyway clearly describes the webhook event type as well on the listing.