FLATPAK-BUILD-COMMIT-FROM(1)

💅 flatpak-build-commit-from — the girlies' guide (section 1 of the manual, okurrr)

okay so bestie, welcome to FLATPAK BUILD-COMMI(1), aka the flatpak build-commit-from page. yes the header is being a lil dramatic with the truncation, we love her anyway. sit down, grab a boba, this one's actually so useful. 🧋✨

---

✨ NAME ✨

flatpak-build-commit-from — create new commits based on existing one (possibly from another repository) 💖

---

🌸 SYNOPSIS 🌸

flatpak build-commit-from [OPTION...] DST-REPO DST-REF...

---

🦋 DESCRIPTION 🦋

so what this does: it creates new commits on the DST-REF branch in DST-REPO, and the contents — plus most of the metadata — get taken from another branch. that other branch can live in another repo, or it can just be another branch in the same repository. lowkey flexible of her. 👑

the collection ID set on DST-REPO (if one is set, that is) will be used for the newly created commits.

ngl this command is iconic when you want to maintain a branch with a clean history that has no unsigned or broken commits. like, for instance, you can import the head from a different repository from an automatic builder once you've verified that it actually worked. the new commit will have no parents or signatures from the autobuilder, and it can be properly signed with the official key. clean girl aesthetic, fr fr. ✨

any deltas that affect the original commit and that match parent commits in the destination repository are copied and rewritten for the new commit id. periodt.

---

💅 OPTIONS 💅

the following options are understood, bestie — read them all, don't skip:

• -h, --help — show help options and exit. the classic "what does anything do" button 🫶
• --src-repo=SRC-REPO — the (local) repository to pull the source branch from. defaults to the destination repository.
• --src-ref=SRC-REF — the branch to use as the source for the new commit. defaults to the same as the destination ref, which is only useful if a different source repo has been specified. iykyk.
• --extra-collection-id=COLLECTION-ID — add an extra collection-ref binding for this collection, in addition to whatever would normally be added due to the destination repository collection id. you can use this option multiple times, she's generous. 💖
• --subset=SUBSET — mark the commit to be included in the named subset. this will cause the commit to be put in the named subset summary (in addition to the main one), letting users see only this subset instead of the whole repo. curated feed energy 🌈
• --untrusted — the source repository is not trusted, so all objects are copied (not hardlinked) and all checksums are verified. safety girl. 🔒
• -s, --subject=SUBJECT — one line subject for the commit message. if not specified, it will be taken from the source commit.
• -b, --body=BODY — full description for the commit message. if not specified, it will be taken from the source commit.
• --update-appstream — update the appstream branch after the build.
• --no-update-summary — don't update the summary file after the new commit is added. this means the repository will not be useful for serving over http until build-update-repo has been run. this is useful if you want to do multiple repo operations before finally updating the summary. (yes the original says "is useful is you want", we're keeping the vibe, no cap.)
• --force — create new commit even if the content didn't change from the existing branch head. stubborn queen. 💀
• --disable-fsync — don't fsync when writing to the repository. this can result in data loss in exceptional situations, but can improve performance when working with temporary or test repositories.

⚠️ okay so about that one: skipping fsync can result in data loss in exceptional situations. it's a speed-for-safety trade, bestie. use it for temporary or test repos, not for the precious ones. 🙈

• --gpg-sign=KEYID — sign the commit with this GPG key. this option can be used multiple times.
• --gpg-homedir=PATH — GPG Homedir to use when looking for keyrings
• --end-of-life=REASON — mark build as end-of-life
• --end-of-life-rebase=OLDID=NEWID — mark new refs as end-of-life. unlike --end-of-life, this one takes an ID that supersedes the current one. by the user's request, the application data may be preserved for the new application. note, this is actually a prefix match, so if you say org.the.app=org.new.app, then something like org.the.app.Locale will be rebased to org.new.app.Locale. glow-up pipeline ✨
• --timestamp=TIMESTAMP — override the timestamp of the commit. use an ISO 8601 formatted date, or NOW for the current time
• --disable-fsync — don't fsync when writing to the repository. this can result in data loss in exceptional situations, but can improve performance when working with temporary or test repositories. (yes she's listed twice in the original and we are NOT erasing her, we respect the source material 💜)
• -v, --verbose — print debug information during command processing.
• --ostree-verbose — print OSTree debug information during command processing. the extra-spicy debug level 🔥

---

🎀 EXAMPLES 🎀

to revert a commit to the commit before:

$ flatpak build-commit-from --timestamp=NOW
--src-ref=app/org.gnome.gedit/x86_64/master^ repo
app/org.gnome.gedit/x86_64/master

look at that ^ doing the heavy lifting. main character energy fr. 👑

---

🌟 SEE ALSO 🌟

ostree(1), flatpak(1), flatpak-build-init(1), flatpak-build(1), flatpak-build-finish(1), flatpak-build-sign(1), flatpak-build-update-repo(1)

---

and that's the whole page, bestie!! 🫶 this lil beauty comes to you from the flatpak source, dated with the FLATPAK BUILD-COMMI(1) footer vibe — go forth, make clean commits, and slay. 💖🌸🦋✨💅