public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Major Hayden <major@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-oci] rawhide: chore: filter packit job history by repo_name
Date: Fri, 06 Nov 2026 22:16:46 GMT [thread overview]
Message-ID: <179400340646.1.16668305508383199724.rpms-python-oci-89f70fcd04e4@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-oci
Branch : rawhide
Commit : 89f70fcd04e4c860515061286072388d784e2280
Author : Major Hayden <major@redhat.com>
Date : 2026-11-06T16:16:35-06:00
Stats : +5/-5 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-oci/c/89f70fcd04e4c860515061286072388d784e2280?branch=rawhide
Log:
chore: filter packit job history by repo_name
- The prod.packit.dev project_url query parameter does not reliably filter results, which can show an unrelated package's latest build and suggest a false Packit reaction.
Signed-off-by: Major Hayden <major@redhat.com>
---
diff --git a/.agents/skills/update-oci-pair/SKILL.md b/.agents/skills/update-oci-pair/SKILL.md
index e54da77..4640793 100644
--- a/.agents/skills/update-oci-pair/SKILL.md
+++ b/.agents/skills/update-oci-pair/SKILL.md
@@ -242,11 +242,11 @@ the dist-git hosting service's open pull requests for the `rawhide` branch.
For example, where these commands are available in the local setup:
```sh
-# Packit job history per package (no packit CLI needed; plain API calls):
-curl -s 'https://prod.packit.dev/api/koji-builds?project_url=https://src.fedoraproject.org/rpms/python-oci' |
- jq -r '.[] | "\(.build_submitted_time | todate) | \(.status) | task \(.task_id)"' | head -5
-curl -s 'https://prod.packit.dev/api/koji-builds?project_url=https://src.fedoraproject.org/rpms/oci-cli' |
- jq -r '.[] | "\(.build_submitted_time | todate) | \(.status) | task \(.task_id)"' | head -5
+# Packit job history (no packit CLI needed; the project_url query param does
+# not reliably filter, so filter client-side by repo_name):
+curl -s 'https://prod.packit.dev/api/koji-builds' |
+ jq -r '.[] | select(.repo_name == "python-oci" or .repo_name == "oci-cli") |
+ "\(.repo_name) | \(.build_submitted_time | todate) | \(.status) | task \(.task_id)"' | head -10
```
Skip the `packit` CLI: `packit status --repo` is not a valid option and the
reply other threads:[~2026-11-06 22:16 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=179400340646.1.16668305508383199724.rpms-python-oci-89f70fcd04e4@fedoraproject.org \
--to=major@redhat.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