Uploaded image for project: 'Community Linux Engineering'
  1. Community Linux Engineering
  2. CLE-3344

Switch from Pagure to Forge for blocker review discussions

SetAsigneesSync from "Extern...update-metadata-from-f...XMLWordPrintable

    • 8
    • Nexus 2026 Sprint 02

      Original reporter: kparal@redhat.com

      The issue:

      Currently we support only Pagure for doing async blocker review discussions. For production, we use the [blocker-review](https://pagure.io/fedora-qa/blocker-review) repo.

      Since we're migrating from Pagure to Forge, we would need a change in blockerbugs that would drop Pagure support and introduce Forge support for blocker discussions.

      This means:
      a) implementing reading, creating and editing a Forge ticket through its API
      b) figuring out how to get notified when a Forge ticket is updated (in Pagure, we do this through a webhook)
      c) figuring out authentication with Forge, and testing for privileged members
      d) fixing ticket formatting if needed

      Don't forget that most of the changes can be tested through staging instances - https://stg.pagure.io , https://bugzilla.stage.redhat.com and https://forge.stg.fedoraproject.org .

              Unassigned Unassigned
              cle_bot CLE bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: