That way at least the automation activity stays entirely within the GitHub / Azure network.
It looks like you can do that for Ruby by adding this:
https://github.com/actions/cache/blob/master/examples.md#rub...
- uses: ruby/setup-ruby@v1
with:
ruby-version: 3.1
bundler-cache: trueAccording to [2], a small VM uses around 7.5 Wh for 30 minutes (for a blended load of active/idle if I understand it correctly), or 0.00023 kWh per minute. So in very rough numbers with a lot of assumptions if your process takes less than 1:30 to install and run your program you are probably comparable to a Google search. More than that and you are almost certainly less energy efficient.
[1] https://www.nytimes.com/2011/09/09/technology/google-details...
[2] https://www.researchgate.net/figure/Mean-Energy-Consumption-...
The few people who look at your GitHub profile may be some important people, like your every future prospective employer. It may make sense to impress them a little bit.
Doing this once a week, like the article mentions, should be good enough for most people. It's not _that_ critical information.