public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Lokesh Mandvekar <lsm5@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/pack] epel8: add packit config
Date: Fri, 24 Jul 2026 17:57:36 GMT [thread overview]
Message-ID: <178491585679.1.18177076340352140817.rpms-pack-5abeb3e3c994@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/pack
Branch : epel8
Commit : 5abeb3e3c9943f5534e5aa86d593de2c1d33ef62
Author : Lokesh Mandvekar <lsm5@redhat.com>
Date : 2025-11-22T16:39:46-05:00
Stats : +79/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/pack/c/5abeb3e3c9943f5534e5aa86d593de2c1d33ef62?branch=epel8
Log:
add packit config
---
diff --git a/.packit.yaml b/.packit.yaml
new file mode 100644
index 0000000..64c1175
--- /dev/null
+++ b/.packit.yaml
@@ -0,0 +1,79 @@
+# See the documentation for more information:
+# https://packit.dev/docs/configuration/
+
+specfile_path: pack.spec
+
+# Name mapping between Fedora and upstream package name
+upstream_package_name: pack
+downstream_package_name: pack
+
+# URL of the upstream repository
+upstream_project_url: https://github.com/buildpacks/pack
+
+# Fedora dist-git base URL
+dist_git_base_url: ssh://pkgs.fedoraproject.org/rpms
+
+# Monitoring upstream releases
+issue_repository: https://github.com/buildpacks/pack
+
+jobs:
+ # Create pull requests with new upstream releases
+ - job: propose_downstream
+ trigger: release
+ # Target Fedora branches
+ dist_git_branches:
+ - rawhide
+ - f43
+ - f42
+ - epel10
+ - epel9
+
+ # Tests to run on created pull requests
+ - job: tests
+ trigger: pull_request
+ targets:
+ - rawhide
+ - f43
+ - f42
+ - epel10
+ - epel9
+
+ # Koji builds for created pull requests
+ - job: koji_build
+ trigger: pull_request
+ dist_git_branches:
+ - rawhide
+ - f43
+ - f42
+ - epel10
+ - epel9
+
+ # Bodhi updates for created pull requests (stable branches only)
+ - job: bodhi_update
+ trigger: pull_request
+ dist_git_branches:
+ - f43
+ - f42
+ - epel10
+ - epel9
+
+# Actions to perform after syncing upstream release
+actions:
+ # Create the source tarball with vendored dependencies
+ create-archive:
+ # Checkout the release tag
+ - git checkout {ref}
+ # Vendor Go dependencies
+ - go mod vendor
+ # Add vendor directory to git (required for git archive)
+ - git add -f vendor/
+ # Commit the changes
+ - git commit -m 'add vendor' || true
+ # Create the tarball with vendored dependencies
+ - bash -c "git archive --prefix=pack-{version}/ -o v{version}-vendor.tar.gz HEAD"
+
+# Archive configuration
+archive_root_dir_template: pack-{version}
+
+# Specify custom archive name to match spec file expectation
+upstream_tag_template: v{version}
reply other threads:[~2026-07-24 17:57 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=178491585679.1.18177076340352140817.rpms-pack-5abeb3e3c994@fedoraproject.org \
--to=lsm5@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