Disable warnings, when the repository on Codeberg has problems #10

Describe the problem

When the repository in Codeberg is not available due to maintenance, DDOS attacks or something else, Weblate sends warnings like

Dieses Projekt ist falsch eingerichtet.
Die URL der Projektwebsite verweist auf einen nicht existierenden Ort:
 https://codeberg.org/Residuum/Sensors2OSC (HTTPSConnectionPool(host='codeberg.org', port=443): Read timed out. (read timeout=5))

Nothing much is needed, just logging into Weblate and remove the warning, but when a user is administering multiple repositories, then this can be an annoyance.

Solution brainstorm

If the repository was synchronized once, and the source is just a slow or unavailable repository in Weblate, could this be filtered for all codeberg weblate?

Alternatively a setting in each weblate project would be a good idea.

Describe alternatives you have considered

No response

Screenshots

No response

Additional context

No response

We are generally tracking all codeberg related issues in https://codeberg.org/Codeberg/Community/issues not for the individual services we run. But forgejo doesn't allow moving this there... so I'll just answer here I guess.

Weblate actually added a global option to disable these checks https://docs.weblate.org/en/weblate-5.17/admin/config.html#std-setting-WEBSITE_ALERTS_ENABLED but I'm unsure if we should disable this.

(The better option would of course be for codeberg.org to be less unstable. 😅)

Thanks for the answer.

Yes, ideally codeberg.org would be less unstable, but for me, the stability is not much a problem per se, as it is run mostly by volunteers and it a not for profit association, and not backed by a big corporation. That alone is worth the instability.