Open bircni opened 1 week ago
good idea as a concept, but I'm not sure if per-commit is very useful
consider the usual scenario of this crate mainly updating to the next version of egui: the commits could be as far as months in between and that means it won't run at all for months, and then it'll run for a bunch of commits in a burst, and then potentially not again for months.
maybe once a week or every night would work better? i'm not sure how much that adds up to in actions-hours. is it possible to have an external trigger of some sort when another repo (such as phosphor core) is updated?
@amPerl maybe this is interesting or by creating a new issue? https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#running-your-pull_request-workflow-based-on-files-changed-in-a-pull-request
On every commit into main this script now gets triggered to check if there are new icons available