@haraldh I'm currently using your first suggestion.
@npmccallum I have very positive news re. the runner: the public image (https://github.com/joeyx22lm/docker-github-actions-runner) should work exactly as we need it to, as long as we can store a Github-provided token securely on the Packet server.
Don't worry about it.
Just presume the token is in a file on the disk somehow.
heh that rhymed
I can basically bake a path into a "script" value with bash but can't assign it as its own cargo make env var unless I do it outside a task
@lkatalin reads all the docs
meh
@npmccallum oh my... looks like I have to expand the macros with cargo expand...
@npmccallum we can't test, that something doesn't compile, or can we?
yeah, I should add more doc tests
at least for the parts, which don't rely on kvm
ah.. rebase might fix it
now we are talking
@connorkuehl Totally fine if you reply to this on Monday, but do you have insight as to why you need both
workspace = false and condition = { env_not_set = ["CARGO_MAKE_CRATE_NAME"]} to create a top-level task? I would expect it to work with just the former. However, as I'm testing, having only workspace = false does nothing and adding the env var not set condition means the task is skipped entirely at the crate level and top level.