PACKIT-PROPOSE-DOWNSTREAM(1)
π PACKIT-PROPOSE-DOWNSTREAM π
okay bestie, welcome to packit propose-downstream β this is the packit propose-downstream manual page from the packit fam, and she is the girl for getting a fresh upstream release all the way into Fedora. let's get into it π
β¨ SYNOPSIS β¨
packit propose-downstream [OPTIONS] [PATH_OR_URL] [VERSION]
πΈ DESCRIPTION πΈ
land a new upstream release in Fedora using the upstream packit config. that's the whole vibe. you bring the release, packit does the landing, slay π
PATH_OR_URL argument is a local path or a URL to the upstream git repository, and if you just don't say anything, it defaults to the current working directory. so like, no pressure, she'll figure it out π«Ά
VERSION argument is optional too β if you ghost it, the latest upstream version gets used by default. iconic behavior honestly β
π OPTIONS π
--dist-git-branch TEXTβ a comma separated list of target branches in dist-git to release into. defaults to all branches, so she's going everywhere β¨--dist-git-path TEXTβ path to the dist-git repo you wanna work in. otherwise she clones the repo into a temporary directory, which is very much the "borrow it and give it back" energy π¦--force-new-sourcesβ upload the new sources even when the archive is already sitting in the lookaside cache. yes, even then. she's committed π₯--pr/--no-prβ create a pull request to the downstream repository, or push directly. if you don't set this at all, it defaults to whatever value is set in configuration. no cap π-f,--forceβ don't discard changes in the git repo by default, unless this is set. so without it, your changes get yeeted; with it, they survive. protect your work bestie π-b,--resolve-bug TEXTβ bug(s) that are resolved with the update, likerhbz#123. you can specify multiple, so bring the whole list π--sync-aclsβ sync ACLs between the dist-git repo and the fork. heads up: this is considered only with the--proption, so it needs her PR bestie to even show up π-p,--package TEXTβ package to sync downstream, in case there's more than one available, like in a monorepo configuration. use it multiple times to select multiple packages. defaults to all the packages listed inside the config π--local-contentβ do not checkout the release tag, just use the current state of the repo. this option is set by default for source-git repos, so if that's you, you're already living this life β¨--upstream-ref TEXTβ git ref of the last upstream commit in the current branch from which packit should generate patches. plot twist: this option implies the repository is source-git π
real talk:--sync-aclsonly does anything alongside--pr, and--upstream-refquietly tells packit "hey, this is a source-git repo." the more you know π
and that's the whole page, bestie!! this was packit version 1.16.3, dated 2026-09-04, straight from the packit propose-downstream manual. go land that release, you absolute main character π§ββοΈβπ
π¦ where this page comes from
- fedora 43: packit 1.16.3-1.fc43 Β· MIT
- fedora 44: packit 1.16.3-1.fc44 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms