SQ-GIT(1)
π SQ-GIT-POLICY-DIFF π
okay bestie, welcome to sq-git-policy-diff, straight out of the User Commands section of the SQ-GIT(1) manual. she's a little icon and she has ONE job: showing you what changed between two policies. let's get into it π
β¨ NAME β¨
sq-git-policy-diff β Shows changes between two policies π
β¨ SYNOPSIS β¨
sq-git policy diff [OPTIONS] OLD NEW
that's it. that's the whole vibe. no cap.
β¨ DESCRIPTION β¨
so like, this command Shows changes between two policies. simple. iconic. periodt. π¦
now here's the part where it gets β¨flexibleβ¨ β it depends on how many arguments you hand her:
- No arguments at all? She compares
HEAD's policy with the working tree's policy file, which isopenpgp-policy.toml. just raw-dogging the defaults, love that for her. - One argument? The policy in whatever commit or file you named gets compared against the working tree's policy file.
- Otherwise (two of them)? The policies of the two commits or files get compared. head to head. main character vs main character. π₯
β¨ OPTIONS β¨
πΈ Subcommand options πΈ
--new-commit=NEW_COMMITβ The new policy as taken from the specified commit. like, "gimme the new policy but pull it from this commit specifically" π--new-file=NEW_FILEβ The new policy as taken from the specified file. same energy, but from a file this time π--old-commit=OLD_COMMITβ The old policy as taken from the specified commit. the before-picture, commit edition β¨--old-file=OLD_FILEβ The old policy as taken from the specified file. the before-picture, file edition π¦OLDβ The old policy.
This is first interpreted as a commit. If there is no such commit, it is interpreted as a filename. (she checks the commit first, then falls back to the file β that's just the order of operations, bestie π)
When using this command from a script, you should prefer--old-commitor--old-fileinstead as they are explicit. fr fr, scripts deserve clarity.
NEWβ The new policy.
This is first interpreted as a commit. If there is no such commit, it is interpreted as a filename. same deal as OLD, no cap.
When using this command from a script, you should prefer--new-commitor--new-fileinstead as they are explicit. the explicit flags are the moment, trust. π
π Global options π
See sq-git(1) for a description of the global options. she's not gonna repeat herself, go read the main page bestie π
β¨ EXIT STATUS β¨
The exit code is 0 if the policies are the same, and 1 if they are different.
so like β 0 means y'all are twinning π«Ά, 1 means something changed π. easy peasy.
β¨ SEE ALSO β¨
For the full documentation see <https://sequoia-pgp.gitlab.io/sequoia-git>. π (the original wraps it across lines as https://sequoia-pgp.gitlab.io/seβ / quoia-git, but it's one link, she's just shy π₯Ί)
β¨ VERSION β¨
0.6.0
and that's the whole page, babe β¨ this was Sequoia PGP, version 0.6.0, dated 0.6.0, living in the SQ-GIT(1) manual β mwah, go diff some policies, you absolute legend πππ
π¦ where this page comes from
- fedora 43: sequoia-git 0.6.0-4.fc43
- fedora 43: sequoia-git 0.6.0-6.fc43 Β· LGPL-2.0-or-later AND Apache-2.0 AND BSD-3-Clause AND BSL-1.0 AND MIT AND MPL-2.0 AND Unicode-3.0 AND Unicode-DFS-2016 AND Zlib AND bzip2-1.0.6 AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND (MIT OR Apache-2.0 OR Zlib) AND (Unlicense OR MIT)
- fedora 44: sequoia-git 0.6.0-4.fc44
- fedora 44: sequoia-git 0.6.0-6.fc44 Β· LGPL-2.0-or-later AND Apache-2.0 AND BSD-3-Clause AND BSL-1.0 AND MIT AND MPL-2.0 AND Unicode-3.0 AND Unicode-DFS-2016 AND Zlib AND bzip2-1.0.6 AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND (MIT OR Apache-2.0 OR Zlib) AND (Unlicense OR MIT)
- nixos 26.05: sequoia-git 0.6.0
- nixpkgs unstable: sequoia-git 0.6.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms