This reverts commit b31a97a576.

@@ -77,0 +66,4 @@
+    FORGEJO_URL = "https://forge.stg.fedoraproject.org/"
+    FORGEJO_API = "https://forge.stg.fedoraproject.org/api/v1/"
+    FORGEJO_REPO = "quality/blocker-review"
+    FORGEJO_REPO_TOKEN = "YOUR SECRET FORGEJO API TOKEN"

@@ -77,0 +67,4 @@
+    FORGEJO_API = "https://forge.stg.fedoraproject.org/api/v1/"
+    FORGEJO_REPO = "quality/blocker-review"
+    FORGEJO_REPO_TOKEN = "YOUR SECRET FORGEJO API TOKEN"
+    FORGEJO_REPO_WEBHOOK_SECRET = "YOUR WEBHOOK SECRET"

@@ -157,0 +298,4 @@
+    state = data.get("issue", {}).get("state", "")
+
+    if not issue_number or not state:
+        msg = "Unable to parse received message (issue number, state)"

@@ -8,2 +10,4 @@
 from blockerbugs.models.bug import Bug
 
+# URL path component that identifies Forgejo issue links
+FORGEJO_ISSUES_PATH = "/issues/"

@@ -25,3 +53,2 @@
 
-def create_discussions_links(milestone, bugs, links_to_reuse={}):
-    app.logger.info('Creating discussion tickets for %d bugs under %s' % (
+def create_forgejo_discussions_links(

@@ -52,3 +106,2 @@
 
-def sync_discussions():
-    if app.config["PAGURE_REPO_TOKEN"] in (bb_Config.PAGURE_REPO_TOKEN, ""):
+def sync_forgejo_discussions() -> None:

@@ -84,3 +176,1 @@
-    not yet marked with ``Release.discussions_closed=True``.
-    '''
-    app.logger.info('Closing discussion tickets in inactive releases...')
+def close_forgejo_discussions(dry_run: bool = False) -> None:

@@ -77,0 +72,4 @@
+    FORGEJO_BOT_ENABLED = True
+    FORGEJO_BOT_LOOP_THRESHOLD = 2
+    FORGEJO_ADMIN_ORG = "quality"
+    FORGEJO_ADMIN_TEAM = "reviewers"

@@ -135,1 +136,3 @@
-                           "PAGURE_REPO", "PAGURE_BOT_USERNAME", "PAGURE_BOT_ENABLED", "PAGURE_URL", "PAGURE_API",
+    additional_env_keys = ["FAS_ADMIN_GROUP", "FORGEJO_REPO_TOKEN", "FORGEJO_REPO_WEBHOOK_SECRET", "FORGEJO_REPO",
+                           "FORGEJO_BOT_USERNAME", "FORGEJO_BOT_ENABLED", "FORGEJO_URL", "FORGEJO_API",
+                           "FORGEJO_ADMIN_ORG", "FORGEJO_ADMIN_TEAM", "DISCUSSION_SYSTEM",

@@ -21,1 +16,3 @@
-PAGURE_BOT_USERNAME = 'blockerbot'
+FORGEJO_URL = "https://forge.stg.fedoraproject.org/"
+FORGEJO_API = "https://forge.stg.fedoraproject.org/api/v1/"
+FORGEJO_REPO = "quality/blocker-review-test"

@@ -0,0 +1,97 @@
+# BlockerBugs Application - High-Level Workflow

@@ -36,2 +35,3 @@
+    --env POSTGRESQL_DATABASE=blockerbugs \
     --publish 5432:5432 \
-    docker.io/library/postgres:13
+    quay.io/fedora/postgresql-13:latest

@@ -43,3 +44,2 @@
 
-  $ podman exec -it blockerbugsdb psql --host=localhost --username=postgres --command='select version();'
-  Password for user postgres:
+  $ podman exec -it blockerbugsdb psql --host=localhost --username=fedora --command='select version();'

@@ -203,6 +204,136 @@ While the virtualenv is active, you can build all documentation with this comman
 You can then inspect the resulting docs in ``build/docs/html``. Open ``index.html`` to see the home page. Not everything is built as HTML and linked from there, so check directory contents as well, or even the docs source directory at ``docs/source``.
 
 
+Forgejo Integration

@@ -15,3 +15,3 @@
 then select a desired milestone and for each proposed blocker/freeze exception you'll see a **Vote** link displayed, which will direct you to the matching discussion ticket.
 
-If a bug report is very complex and requires real-time communication instead of asynchronous ticket discussions, we'll tag the ticket with the [meeting tag](https://pagure.io/fedora-qa/blocker-review/issues?status=Open&tags=meeting) and the discussion will take place during a blocker bug meeting (see above) instead of here.
+If a bug report is very complex and requires real-time communication instead of asynchronous ticket discussions, we'll tag the ticket with the [meeting tag](https://forge.fedoraproject.org/quality/blocker-review/issues?status=Open&tags=meeting) and the discussion will take place during a blocker bug meeting (see above) instead of here.

@@ -72,3 +72,3 @@
 
 ### Administrative commands
-Members of the [fedora-qa](https://pagure.io/group/fedora-qa) Pagure group can issue administrative commands. Those commands are handled in the same way as voting commands, i.e. they need to be placed on a separate line and are case-insensitive. Those commands include:
+Members of the [fedora-qa](https://forge.fedoraproject.org/quality/) Forge organization can issue administrative commands. Those commands are handled in the same way as voting commands, i.e. they need to be placed on a separate line and are case-insensitive. Those commands include:

@@ -0,0 +1,23 @@
+[pytest]

@@ -2,6 +2,7 @@
 # this automatically also pulls rope and flake8 (which pulls pyflakes, pycodestyle and mccabe)
 python-language-server[rope,flake8]
 mypy
+testcontainers ~= 4.14.0

@@ -17,6 +17,7 @@ munch
 psycopg[binary,pool]
 py
 pycurl
+pyforgejo

@@ -30,23 +30,24 @@ PostgreSQL should be used both for development and production. You can set it up
 Run a `Podman`_ container with the latest `PostgreSQL image`_ (replace ``your-password`` with an actual value)::
 
   podman run --detach --name blockerbugsdb \

@@ -36,2 +35,3 @@
+    --env POSTGRESQL_DATABASE=blockerbugs \
     --publish 5432:5432 \
-    docker.io/library/postgres:13
+    quay.io/fedora/postgresql-13:latest

@@ -0,0 +43,4 @@
+VoteCommand = collections.namedtuple("VoteCommand", ["tracker", "vote"])
+VoteCommand.__doc__ = (
+    VoteCommand.__doc__ or ""
+) + ': A parsed vote command, e.g. tracker="betablocker", vote="+1"'

@@ -0,0 +37,4 @@
+            )
+
+        if not base_url.strip():
+            raise ForgejoAPIException("FORGEJO_API cannot be empty")

@@ -0,0 +2,4 @@
+
+Testcontainer fixtures (forgejo_container, postgres_container, etc.) have been
+moved to testing/conftest.py to make them available for all test modules including
+integration tests and end-to-end tests.