-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate 'packit/deployment' to 'Webhook To Fedora Messaging' #611
Comments
I'll reply here as it makes sense to me to keep the track in this repo and close the others as subtasks… If I wish to skip the whole bureaucratic process of migrating via the ticket (we're talking about removal of one app, and configuring a webhook (to which you don't have permissions anyways…)) I should do the following:
Did I get it right? OTOH I don't really like the fact I had to search for that repo on the GitHub anyways, cause there's no link from the API nor any docs I've managed to find at the first look. Also the docs didn't help much :/ |
Yes, you got that right. We've opened a tracker because the login process via Swagger UI isn't very well streamlined, but if you prefer doing it directly then yeah please do! :-) |
Thanks a lot, appears to be done, got 202 back from the initial ping 🎉 Closes packit/rpm-shim#19 |
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: