diff --git a/.github/workflows/release.yml.disabled b/.github/workflows/release.yml.disabled
index 98e2409..ed7b334 100644
--- a/.github/workflows/release.yml.disabled
+++ b/.github/workflows/release.yml.disabled
@@ -25,7 +25,6 @@ jobs:
           # FIXME: Set your Fedora user account name here
           echo 'yourfedorauser' > ~/.config/bodhi-user
           echo '${{ secrets.GITHUB_TOKEN }}' > ~/.config/github-token
-          echo '${{ secrets.COPR_TOKEN }}' > ~/.config/copr
           echo '${{ secrets.FEDORA_PASSWORD }}' > ~/.fedora-password
 
       - name: Run cockpituous
diff --git a/README.md b/README.md
index 874a23c..23feb35 100644
--- a/README.md
+++ b/README.md
@@ -133,15 +133,18 @@ change:
 
 Once your cloned project is ready for a release, you should consider automating
 that.  [Cockpituous release](https://github.com/cockpit-project/cockpituous/tree/main/release)
-aims to fully automate project releases to GitHub, Fedora, Ubuntu, COPR, Docker
-Hub, and other places. The intention is that the only manual step for releasing
-a project is to create a signed tag for the version number; pushing the tag
-then triggers a [GitHub action](https://github.com/features/actions) that calls a set of release scripts.
+and [Packit](https://packit.dev/) aim to fully automate project releases to
+GitHub, Fedora, Ubuntu, COPR, Docker Hub, and other places. The intention is
+that the only manual step for releasing a project is to create a signed tag for
+the version number; pushing the tag then triggers a [GitHub
+action](https://github.com/features/actions) that calls a set of release
+scripts.
 
-starter-kit includes an example [cockpitous release script](./cockpituous-release),
-with detailed comments how to use it. There is also an
-[example GitHub release action](.github/workflows/release.yml.disabled) to set
-up secrets and run cockpituous.
+starter-kit includes an example [cockpitous release script](./cockpituous-release)
+
+and a [packit.yaml](./packit.yaml) control file with detailed comments how to
+use it. There is also an [example GitHub release action](.github/workflows/release.yml.disabled)
+to set up secrets and run cockpituous.
 
 # Automated maintenance
 
diff --git a/cockpituous-release b/cockpituous-release
index 86e26a5..aca4f08 100644
--- a/cockpituous-release
+++ b/cockpituous-release
@@ -32,6 +32,3 @@ job release-srpm -V
 
 # this needs no explicit secrets, just the GitHub action provided default one
 # job release-github
-
-# This needs secrets.COPR_TOKEN in .github/workflows/release.yml
-# job release-copr @myorg/myrepo
diff --git a/packit.yaml b/packit.yaml
index 2d24d21..ff4fdc7 100644
--- a/packit.yaml
+++ b/packit.yaml
@@ -32,3 +32,14 @@ jobs:
       - fedora-all
       - centos-stream-8
       - centos-stream-9
+
+  # Build releases in COPR: https://packit.dev/docs/configuration/#copr_build
+  #- job: copr_build
+  #  trigger: release
+  #  metadata:
+  #    owner: your_copr_login
+  #    project: your_copr_project
+  #    preserve_project: True
+  #    targets:
+  #    - fedora-all
+  #    - centos-stream-9-x86_64