Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

🐈 Task: Run model repo syncing workflow in a cron job #1466

Closed
DhanshreeA opened this issue Dec 19, 2024 · 3 comments
Closed

🐈 Task: Run model repo syncing workflow in a cron job #1466

DhanshreeA opened this issue Dec 19, 2024 · 3 comments

Comments

@DhanshreeA
Copy link
Member

DhanshreeA commented Dec 19, 2024

Summary

This workflow that is used to update model repos with the latest workflow updates within eos-template should just run as a cron job every day to make sure all our model repos are always updated. This is mostly for my sanity really because I am tired of running workflows in repositories only to realize minutes later that they are outdated. 🫠

Objective(s)

No response

Documentation

No response

@GemmaTuron
Copy link
Member

I think we should make a note somewhere about this as once we finish the development of Ersilia we should not be updating everything once a day, so let's not forget to turn it off or decrease the frequency after a while.

@GemmaTuron
Copy link
Member

In principle with the newest workflow updates reported in #1484 the actual workflows will not need to be modified that much, because they will all use the test module and the testing playground, so that only those will be modified, making it simpler.

@DhanshreeA
Copy link
Member Author

I will mark this as not planned for now.

@DhanshreeA DhanshreeA closed this as not planned Won't fix, can't repro, duplicate, stale Jan 8, 2025
@github-project-automation github-project-automation bot moved this from On Hold to Done in Ersilia Model Hub Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants