sandogasa-report(1)
β¨ sandogasa-report(1) β¨
okay bestie, welcome to sandogasa-report(1), straight out of the Sandogasa Manual π β it's the little tool that tells you what you've been up to in Fedora, EPEL, and CentOS SIG packaging land. group-chat energy, but make it a manpage. let's go π
πΈ NAME πΈ
sandogasa-report β Activity reporting for Fedora, EPEL, and CentOS SIG packaging work
π¦ SYNOPSIS π¦
sandogasa-report [-h|--help] [-V|--version] <subcommands>
π DESCRIPTION π
Activity reporting for Fedora, EPEL, and CentOS SIG packaging work
like. that's the whole vibe. u tell it who u are and it tells u what u did. iconic behavior honestly π«Ά
β OPTIONS β
-h,--helpβ Print help β¨-V,--versionβ Print version π
π COMMANDS π
π sandogasa-report config
sandogasa-report config [-c|--config] [-h|--help]
Interactively set per-user overrides in ~/.config/sandogasa-report/config.toml π
-c,--config <PATH>β Main config file to enumerate domains / forge instances from. Without one, there are no instances to configure π (fr fr, no config = nothing to set up)-h,--helpβ Print help β¨
π sandogasa-report report
sandogasa-report report [-c|--config] [-u|--user] [--by] [--since]
[--until] [--period] [--no-bugzilla] [--no-bodhi] [--no-koji]
[--no-gitlab] [--no-github] [--no-forgejo] [--no-sourcehut]
[--detailed]... [--json] [-o|--output] [-v|--verbose] [-h|--help]
<-d|--domain>
Generate an activity report across one or more domains ποΈβ¨ main character energy, except the main character is your commit history.
-c,--config <PATH>β Path to main config file (domains, groups)-u,--user <USER>β FAS username to report on πββοΈ-d,--domain <DOMAIN>β Domain(s) to report on (defined in config)--by <AXIS>β Add a breakdown grouped this way (repeat or comma-separate)
Possible values:
repo: One row per repository, summed across domains and forges
--since <SINCE>β Start date (inclusive,YYYY-MM-DD)--until <UNTIL>β End date (inclusive,YYYY-MM-DD, default: today)--period <PERIOD>β Reporting period (e.g.2026Q1,2026H1)--no-bugzillaβ Skip Bugzilla queries π--no-bodhiβ Skip Bodhi queries π--no-kojiβ Skip Koji queries π--no-gitlabβ Skip GitLab queries π--no-githubβ Skip GitHub queries π--no-forgejoβ Skip Forgejo queries π--no-sourcehutβ Skip Sourcehut queries π--detailedβ Add detail. Once: counts per repo, project or component under each heading. Twice: the items themselves β every PR, bug, patch and ticket, and every build of a Bodhi update π₯ like, don't say I didn't warn u, twice is a lot of detail and it is lowkey gorgeous--jsonβ Output as JSON instead of Markdown-o,--output <PATH>β Write output to file instead of stdout-v,--verboseβ Print progress to stderr-h,--helpβ Print help (see a summary with-h)
π friendly lil heads-up bestie: --detailed stacks. one of them gives u counts, two of them gives u literally everything β every PR, bug, patch, ticket, and every build of a Bodhi update. gorgeous. overwhelming. slay.
that's the whole page β¨ go forth and report ur activity, ur doing amazing sweetie π
this was sandogasa-report(1) from the Sandogasa Manual, cutie β sandogasa 0.27.0, dated 2026-10-21 π keep slaying, and remember: the manpage says sandogasa-report(1) at the bottom too, bc symmetry π
π¦ where this page comes from
- fedora 43: sandogasa 0.27.0-2.fc43 Β· (Apache-2.0 OR MIT) AND LicenseRef-Fedora-Public-Domain AND Unicode-3.0 AND Apache-2.0 AND ISC AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR ISC OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND BSD-3-Clause AND MPL-2.0 AND (Unlicense OR MIT) AND Zlib
- fedora 44: sandogasa 0.27.0-2.fc44 Β· (Apache-2.0 OR MIT) AND LicenseRef-Fedora-Public-Domain AND Unicode-3.0 AND Apache-2.0 AND ISC AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR ISC OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND BSD-3-Clause AND MPL-2.0 AND (Unlicense OR MIT) AND Zlib
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms