You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please follow this link to the official announcement of the project’s release and use the instructions there to migrate to the new service. If this notification was a mistake, please close this notification ticket. We will not act on the repositories whose migrations have not been requested and any related GitHub2FedMsg operations will stop working once the service is decommissioned.
The text was updated successfully, but these errors were encountered:
Do I understand correctly that the messages are expected to be sent for all GitHub projects related to Fedora Infra, so that interested parties can eg. set up notifications based on Fedora Messaging / FMN? Or can we ignore the webhook setup and not send any Fedora Messaging messages since we don't use it?
@mizdebsk This repository was previously set up on GitHub2FedMsg for its activities to be published on the FedMsg bus. If you rely on the activities being published on the FedMsg or Fedora Messaging bus for various purposes, I would recommend migration to the new service. Although, this is not a requirement or expectation, by any means, if it is not being used.
I'm not aware of anyone relying on Fedora Messaging messages for this GitHub project, so I'm closing this issue without any change. If anyone is interested in receiving these messages, feel free to reopen this issue.
This project was listed in the GitHub2FedMsg database and we want to you to inform you about the upcoming deprecation of the service. As the Fedora Infrastructure is finishing up with migrating its applications away from FedMsg to Fedora Messaging, we encourage you to migrate your repository to the successor of the GitHub2FedMsg project, Webhook To Fedora Messaging.
Please follow this link to the official announcement of the project’s release and use the instructions there to migrate to the new service. If this notification was a mistake, please close this notification ticket. We will not act on the repositories whose migrations have not been requested and any related GitHub2FedMsg operations will stop working once the service is decommissioned.
The text was updated successfully, but these errors were encountered: