cjdesno/silverfish:ci into main CI workflow to install a rust toolchain and run a cargo build, verified on my runner using the ghcr.io/catthehacker/ubuntu:act-22.04 image, which is one of the runner images recommended by the forgejo actions docs.
see here to see the run succeeding in my forked repo: https://codeberg.org/cjdesno/silverfish/actions/runs/8/jobs/0
if you provide me with a runner registration token for the org (you can dm it to me on discord, my handle is cascode), i will register an ubuntu22 runner to it to run this.
or i can switch the ci yaml to the docker tag and see what happens, if you would prefer that. either way, though, i would be happy to contribute an additional runner.
@ -0,0 +14,4 @@
name:Cargo build
runs-on:ubuntu22
steps:
- uses:actions/checkout@v4
I'm confused about when actions can be shorthand and when they need to be full URLs...
AFAICT the answer is if it's an action that forejo directly supports (e.g, is in this repo: https://code.forgejo.org/actions) you can shorthand it, if not it needs to be a full URL.
Token issued.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?