Zlopez
Zlopez
Maybe it would be best to report this on [Fedora Infrastructure](https://pagure.io/fedora-infrastructure/issues), as it seems to affect all the systems using FAS. The cockpit solution is not applicable as they are...
I can definitely open the ticket on your behalf. But just to make clear, can you login to any service using Fedora account at all? You can't login to https://pagure.io...
Looking at the discussion, you are able to login to https://accounts.fedoraproject.org, but that doesn't redirect to https://id.fedoraproject.org. So that could be the difference.
I didn't have time to work on this, too much on my plate right now. Could you sent e-mail with your issue to [email protected]? Or open ticket on https://pagure.io/fedora-infrastructure/issues.
I can see that the versions are in the checked URL. My assumption is that there was some change in SourceForge and the check doesn't work correctly anymore. I will...
Could you colaborate on that?
I still don't follow, this depends on the backend used by project.
Do I understand it correctly that you want some account that the chatGPT can just use on release-monitoring.org?
I assume that you can create an account for chatgpt and generate API token for it on that account. It should be then able to use [release-monitoring API ](https://release-monitoring.org/static/docs/api.html)
In Fedora we will move to Forgejo as well. So this makes sense. This needs a new Forgejo backend to work.