Closed srid closed 1 week ago
Another thing we might want om ci run
to do here is to output metadata in some form, such as JSON of out paths (including even measurements à la nixv
) that can then be used to get dockerImage tarball, static binary zip, gh-pages static site export, etc. from other Actions workflows.
This is by and large done by now, and documented: https://omnix.page/om/ci.html
For individual features, let's open separate issues on GitHub.
216
197
198
200
[^1]: cf.
onlyBuild
&doNotBuild
of nix-ci.com (via X)