PACKIT-PROPOSE-DOWNSTREAM(1)

πŸ“¦
version 1.16.3 Β· 5 versions
, in fedora 43, fedora 44

πŸ’– 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, like rhbz#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 --pr option, 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-acls only does anything alongside --pr, and --upstream-ref quietly 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