From Fedora Project Wiki

Revision as of 08:20, 14 October 2024 by Sumantrom (talk | contribs) (Created page with " As a package maintainer, I’d like to be able to control the-new-hotness monitoring status from distgit. == Gitlab == For this to work on GitLab, we would need to have metadata stored in repository. This could be for example stored in .metadata file. Anybody with commit rights to repository will be able to change the monitoring settings. Or we can leverage GitLab badges feature (https://docs.gitlab.com/17.2/ee/user/project/badges.html) which could be accessed...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

As a package maintainer, I’d like to be able to control the-new-hotness monitoring status from distgit.

Gitlab

   For this to work on GitLab, we would need to have metadata stored in repository. This could be for example stored in .metadata file. Anybody with commit rights to repository will be able to change the monitoring settings.
   Or we can leverage GitLab badges feature (https://docs.gitlab.com/17.2/ee/user/project/badges.html) which could be accessed by the-new-hotness through API and the maintainer can set the correct monitoring badge for the project.

Forgeo

   For this to work on Forgejo, we would need to have metadata stored in repository. This could be for example stored in .metadata file. Anybody with commit rights to repository will be able to change the monitoring settings.
   Or we can leverage Forgejo badges feature (https://forgejo.org/docs/latest/user/readme-badges/), which isn’t supported by Forgejo API yet. We can ask Forgejo developers to add support for badges. The-new-hotness will need to be able to access the badges by different means till then (for example checking specific badges URLs).