mirror of
https://github.com/outbackdingo/hyprcosmic.git
synced 2026-08-25 14:53:21 +00:00
gitops
3c1a092e51
Two jobs, shaped differently on purpose. cosmic-conf gets the same three-distribution container matrix the forks use, plus one check the unit tests cannot make: it resolves the cosmic.conf this repository actually ships. A schema change that invalidated the shipped config would pass all 143 tests in the crate and still break every user on their first login. The binary is invoked directly rather than through `cargo run`, because the step redirects HOME and cargo keys its registry cache on it -- `cargo run` would re-download every dependency into a directory the cache action does not know about. The assets job is where the rules that were previously only remembered become enforced. config.jsonc is regenerated and must not move, which is what stops it being hand-edited; the template and the generator are held to pure ASCII, which is what stops a Nerd Font glyph being pasted somewhere it will be silently destroyed by the next person who retypes it. install-assets.sh is then run into a staging root and asked to verify its own work, which also exercises the audit that refuses to install at all while any file under config/ is unclassified. The ASCII check is written as an `if` rather than `! grep`, because grep exits 1 for "no match" and 2 for "no such file" -- negating it would turn a vanished file into a pass, and the check would quietly stop checking anything.