today is the first time i encountered recursive submodules in the wild (i'm looking at a repository that includes itself as a submodule 13 times)
working with this repo does not spark joy
you know how it is

i am slowly becoming a "(GitHub|Forgejo) Actions expert" in the same way and sense as i have become a CMake expert

distressing.

@whitequark normally, I’d say something about being an Expert by Virtue of Least Ignorance, but you clearly don’t require such caveats: you’re an expert, though possibly against your better interests
@whitequark I dislike the Actions model and prefer GitLab’s CI system which is basically just shell wrapped in YAML. That’s maybe wrong-headed of me; I don’t know.
We still use Jenkins at work and, for my sins and indiscretions, I have to deal with a bunch of Groovy scripting and plugins. My longer term takeaway from this is that CI should reuse the same scripting or patterns that a maintainer uses to perform the build and testing runs and not something else. I don’t know if that’s something that generalizes fully, but I’d make it that way in a heartbeat if I could at work.
@c0dec0dec0de I mean nothing stops you from making an Actions workflow that's one big run: step
@whitequark that’s a good point. As long as any reporting can be done from logs of that stage or cached artifacts, that would get the best of both worlds.
@whitequark at some point in the indeterminate future, I will probably need to assist in migrating from Jenkins to GitLab CI and we’re going to lose the convenient all-in-one-app metrics/diagnostics except as downloadable reports (as I understand it).

@whitequark

find_package(ArguablyUnnecessaryGHAIntegrationHelpers)

in all seriousness, a cmake helper for deploying to Pages has _a_ reason to exist?

@r hmm, it's one add_custom_target but it would first need to acquire git-pages-cli... could be useful

@whitequark fwiw, "needing to compile the compiler first" (or, usually, a less extreme but approximately equivalent form, "needing to either compile or acquire dependencies for (e.g. via PyPI) a bespoke preprocessing tool") is basically _the_ use case that causes us to prefer "ad-hoc garbage build system" over something more principled

so more examples of that throughout the ecosystem might be beneficial if you have "principled build systems" as a goal

@r i mean in case of git-pages-cli (a client application which has no meaningful security relevance because it's equivalent to tar|curl) i would probably hardcode the checksums for a few architectures and be done with it
@whitequark I am sorry for your loss
@whitequark
Someone has to fight the forces of evil.
Congratulations.