public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Coiby Xu <coiby.xu@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/dmidecode] f44: Use packit to automate dmidecode releasing
Date: Sat, 13 Jun 2026 10:47:39 GMT	[thread overview]
Message-ID: <178134765960.1.8255885118205299381.rpms-dmidecode-d46072f2d2e7@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/dmidecode
            Branch : f44
            Commit : d46072f2d2e73e6723044a833f6282db0b9efc18
            Author : Coiby Xu <coiby.xu@gmail.com>
            Date   : 2026-06-12T08:36:54+08:00
            Stats  : +37/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/dmidecode/c/d46072f2d2e73e6723044a833f6282db0b9efc18?branch=f44

            Log:
            Use packit to automate dmidecode releasing

Follow [1] to use packit to automate releasing dmidecode. After finishing
one-time setting up, when there is a new upstream release, here's the
new process of releasing a new version in Fedora,

1. https://release-monitoring.org/ finds a new upstream version and
   notify packit

2. packit: automatically create PRs to propose new release for different
   Fedora releases;  also upload new tarballs into lookaside cache.

3. Maintainer: review(, modify) and merge the PR

4. packit: create a koji build

5. packit: create a Bodhi update

So maintainers only need to do step 3 manually and all the repetitive
work can be left to packit to handle.

After the PR gets merged, two more things need to be done [2],
 - Create a Fedora mapping for the upstream project in
   https://release-monitoring.org/projects (already done)
 - Set Monitoring status on the left side at
   https://src.fedoraproject.org/rpms/dmidecode to Monitoring (already
   done)

[1] https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding
[2] https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding#2-monitoring-of-the-package

Signed-off-by: Coiby Xu <coiby.xu@gmail.com>

---
diff --git a/.packit.yaml b/.packit.yaml
new file mode 100644
index 0000000..5534eb3
--- /dev/null
+++ b/.packit.yaml
@@ -0,0 +1,37 @@
+# See the documentation for more information:
+# https://packit.dev/docs/configuration/
+
+specfile_path: dmidecode.spec
+
+# add or remove files that should be synced
+files_to_sync:
+    - dmidecode.spec
+
+# name in upstream package repository or registry (e.g. in PyPI)
+upstream_package_name: dmidecode
+# downstream (Fedora) RPM package name
+downstream_package_name: dmidecode
+
+upstream_tag_template: v{version}
+
+
+jobs:
+  # This is triggered by https://release-monitoring.org/
+  - job: pull_from_upstream
+    trigger: release
+    dist_git_branches:
+      - fedora-all
+
+  # This is triggered at Fedora dist-git for creating koji build after
+  # PR in src.fedoraproject.org been merged.
+  - job: koji_build
+    trigger: commit
+    allowed_pr_authors: ["all_committers", "packit"]
+    dist_git_branches:
+      - fedora-all
+
+  # This is triggered at Fedora messaging bus about koji build finished.
+  - job: bodhi_update
+    trigger: commit
+    allowed_builders: ["all_committers", "packit"]
+    dist_git_branches:

                 reply	other threads:[~2026-06-13 10:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178134765960.1.8255885118205299381.rpms-dmidecode-d46072f2d2e7@fedoraproject.org \
    --to=coiby.xu@gmail.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox