Looks like Forgejo API doesn't provide a way to examine previous workflow runs. So I'm not sure if I can keep the "skip if duplicate" functionality I use to waste fewer CI resources.

(The equivalent GHA seems to use variables not implemented by Forgejo.)

Maybe I could so "sha256sum --check hashfile.txt" and actions/cache shenanigans. But that seems a bit fragile (and also requires me to detect whether the current run succeeded; no point in rewriting file hashes if the run failed)...
Yea, I'm just gonna go back to using "[no ci]" strings :D...