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

Best practice for updating strategy code #447

Open
seventhsite opened this issue Dec 3, 2024 · 2 comments
Open

Best practice for updating strategy code #447

seventhsite opened this issue Dec 3, 2024 · 2 comments

Comments

@seventhsite
Copy link
Contributor

What’s the best way to update the strategy file from the repo?

  • After every commit?
  • Or only during releases?

Looking for advice on the cleanest approach. Thanks!

@iterativv
Copy link
Owner

Hi, you can do either. Set a cron job or similar, one a hour maybe, when there are new commits.

@seventhsite
Copy link
Contributor Author

Thanks for the response!

I’ve already set up an Ansible playbook to handle this. Just wanted to mention that my main concern was whether to rely only on releases or if non-release commits are generally safe to pull without risking something destructive.

Thanks again!

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

No branches or pull requests

2 participants