asonix/blog
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Fix typos
All checks were successful
/ publish (push) Successful in 10s
Details

Browse source
This commit is contained in:
asonix 2024-02-10 15:02:55 -06:00
parent b5f00faefe
commit 5031da5073
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/001-forgejo-actions.md
View file

@ -9,8 +9,8 @@ tags = ["admin", "ci", "docker", "forgejo", "actions"]
Over the last few days I've figured out how to use Forgejo Actions. I was excited to try it since
it's integrated directly into Forgejo these days, and compatibility with github Actions means
there's already loads of third party actions to take advantage of. Previously I was using Drone CI.
I still am in a number of projects. But I'm hoping to get everything moved over over the next week
or so.
I still am in a number of projects. But I'm hoping to get everything moved over to it over the next
week or so.
But that's not why I'm writing this blog post. I'm writing this blog post because I haven't found
very many useful resources for understanding how Actions works, despite the prevalence github
@ -183,7 +183,7 @@ Hmm...
## The Problems
So actions/checkout@v4 depends on node to run, but my rust builder container doesn't have node in it
so... I can't checkout my code? Well let't just split this up a bit, then.
so... I can't checkout my code? Well let's just split this up a bit, then.
```yaml,linenos
on:
push: