Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update cronjob schedule #15

Closed
sylhare opened this issue Jan 14, 2021 · 1 comment
Closed

Update cronjob schedule #15

sylhare opened this issue Jan 14, 2021 · 1 comment

Comments

@sylhare
Copy link

sylhare commented Jan 14, 2021

Hi!

Nice work, but I believe running the github action every hour is a bit overkill. (Over 3000 commits on just generated image)
Maybe everyday or every month could be a bit more reasonable.

What do you think?

@jstrieb
Copy link
Owner

jstrieb commented Jan 19, 2021

Thanks for opening this issue! You raise a good point that I did give much thought to. I think adjusting the main repository so that it updates every day instead of every hour is reasonable – expect a commit implementing this shortly.

I would be hesitant for it to update less frequently than that since I'm pretty active on GitHub and the stats images would have the potential to become outdated and inaccurate fairly quickly.

Note that in practice, it (hopefully) shouldn't matter too much either way:

  • It is possible to view only the real commits I have actually made here.
  • Since the repository is now a "template," it doesn't bring any Git history with it when cloned via the recommended "Use this template" button.
  • Since this repository is public, I can effectively use unlimited GitHub Actions minutes without hitting the monthly ~3,000 minute limit for private repositories.

For completeness' sake, see issue #6 – a discussion justifying committing updated images directly to the repo. It's definitely not ideal, but I've yet to find a better method that works.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants