PACKIT-DIST-GIT-INIT(1)

👑 packit dist-git init — from the packit dist-git init Manual (section 1, bestie) 💖

🌸 NAME 🌸

packit-dist-git-init — Create the initial Packit dist-git... (yes the original literally trails off like that, we love a mysterious queen)

---

✨ SYNOPSIS ✨

packit dist-git init [OPTIONS] [OTHER_ARGS]... [PATH_OR_URL]

---

🦋 DESCRIPTION 🦋

Okay so bestie, here's the vibe: this command creates the initial Packit dist-git configuration for Fedora release syncing, based on whatever input parameters you hand it. It's giving setup wizard but make it Fedora. 💅

What it does is it adds a .packit.yaml file to the dist-git repository, and it can do that in two ways:

1. a repo specified by path (and that defaults to the current working directory, no cap), or
2. a repo specified by URL — as in https://src.fedoraproject.org/rpms/<package> — in which case it clones the repository and drops the config in there. 🫶

Real talk though: for the URL route you ideally want to use the --clone-path option, because otherwise the repository gets cloned into a temporary directory that then gets removed. So your work would just... evaporate. 😭 Use --clone-path, bestie, I'm begging.

By default, all 3 jobs for release syncing get configured: pull_from_upstream, koji_build, and bodhi_update. If you don't want some of them, you've got --no-pull, --no-koji-build or --no-bodhi-update to skip them. Choose your own adventure. 🌈

And then there's the whole "how do you want to ship it" situation:

• create the Packit config file only locally (this is the default),
• create a pull request (with the --create-pr option), or
• push directly to the dist-git's default branch (with --push-to-distgit). 🔥

Also, heads up: go look at packit init if what you actually want is to initialize a repository as an upstream repo. Different girl, different job.

💖 Examples 💖

Local Packit configuration generation for a dist-git repo in the current working directory:

$ packit dist-git init

Local Packit configuration generation for a dist-git repo in the current working directory configuring git URL for cloning of the upstream repository:

$ packit dist-git init --upstream-git-url
https://github.com/packit/packit .

Local Packit configuration generation for a dist-git repo specified by URL that will be cloned to <my-package> dir:

$ packit dist-git init --clone-path
`<my-package>` https://src.fedoraproject.org/rpms/packit

Using arbitrary configuration options that are not provided as the command options (the working dir needs to be specified in this case):

$ packit dist-git init --upstream-git-url
https://github.com/packit/packit
--my-option option-value .

---

💅 OPTIONS 💅

• --upstream-git-url TEXT — URL to the upstream GIT repository 🌸
• --upstream-git-url-command TEXT — a command you run to get the URL of the upstream git repository, for when you're feeling indirect 💫
• --upstream-tag-template TEXT — template applied for upstream tags if they differ from versions. E.g. 'v{version}' 🎀
• --upstream-tag-include TEXT — Python regex used for filtering upstream tags to include. ✨
• --upstream-tag-exclude TEXT — Python regex used for filtering upstream tags to exclude. 🙈
• --version-update-mask TEXT — Python regex used for comparison of the old and the new version. 👑
• --version-update-specifiers TEXT — PEP 440 version specifier set (e.g. '>=1.0, <2.0') used to filter the proposed version. 🧚
• --issue-repository TEXT — URL of a git repository that can be used for reporting errors in form of issues. 🐛
• --no-pull — Do not include the pull from upstream job in the config. 💀
• --no-koji-build — Do not include the Koji build job in the config. 💀
• --allowed-committers TEXT — comma separated list of allowed_committers used for Koji builds. 🫶
• --allowed-pr-authors TEXT — comma separated list of allowed_pr_authors used for Koji builds. 🫶
• --no-bodhi-update — Do not include the Bodhi update job in the config. 💀
• --actions-file FILE — yaml file with 'actions' that should be used for the config. 🍓
• --dist-git-branches TEXT — comma separated list of target branches in dist-git to release into. (defaults to rawhide) 🌿
• --dist-git-branches-mapping TEXT — JSON dictionary of target branches in dist-git to release into for which fast_forward_merge_into syntax will be used, e.g. '{"fedora-rawhide": ["f39", "f40"]}'. If not provided and --dist-git-branches is not provided as well, defaults to '{"fedora-rawhide": ["fedora-branched"]}'. 🗺️
• -p, --push-to-distgit — Push the generated Packit config to the dist-git repository's rawhide. 🚀
• -c, --create-pr — Create a PR with generated Packit config. 💌
• -f, --force — Reset config to default if already exists. ⚠️ (yes it will overwrite, bestie, be brave)
• --clone-path TEXT — Path to clone the dist-git repo into (if path_or_url is URL). Otherwise clone the repo in a temporary directory. 🏠
• --commit-msg TEXT — Commit message used when creating a PR (also for the title) or pushing to dist-git. Default: 'Add Packit configuration for automating release syncing' ✍️

---

and that's the whole page, bestie, you ate that 💜

this was page 1 of the packit dist-git init Manual, version 1.16.3, dated 2026-09-04 — mwah, go slay some release syncing 👑✨