| |
Test it out
| |
Then run
act
I chose the medium instance. It seemed to pass.
Listing out the repos
My first test is to print out all of my repos in the run. This isn't that exiting but it's a good way to test it out.
| |
Run it like
| |
This gives a gh not found error, which is not great, so lets switch to the full
image instead of the medium one.
Pull it manually since there's no progress report otherwise
| |
Then fire it up:
| |
This also required me to increase the disk image size for the vm that I'm running all this stuff under.
Ultimately, the fact that act doesn't run exactly the same as the
github runners is frustrating.
Creating a quick generator
We'll load in a TEMPLATE.md file, and then replace the comments repo
activity and feed: url with a list of things that we get from github
or from an external rss feed.
| |
Then generate.rb:
| |
Test it locally to make sure that it runs every so nicely.
The build script
A couple of points
- Adding
workflow_dispatchlets you trigger this in the admin tool on github proper - The default
GITHUB_TOKENdoesn't show visibility to other repos. go to settings, and copy your personal token in as a secret (calledWILL_TOKENbelow) to be able to have theghcommand see your other repos
| |
And now you can see my updated github profile!
Thoughts
cron jobs on github are fun. A cool idea would be to have it generate a status page for all your sites and give you a notification if something went down.