Thank you for joining us on the latest Power Hour, featuring @jasper!
Have any questions? Drop them below or feel free to create a new topic here.
3 Likes
Big thank you to @jasper for sharing his scripting + GitHub wisdom today!! Appreciate everyone who attended and for those who couldn’t make it, be sure to watch the recording.
As promised, here is the script wrapper from Jasper, which allows store their scripts in a private GitHub repo until runtime.
1 Like
Curious how long before it gets uploaded to YouTube?
Hey! As soon as I return on Monday, will have the link here for you 
stay tuned
Recording as promised 
https://youtu.be/slonJMIkTDs
1 Like
Thank you! You’re the best and thank you on behalf of everyone (because I’m the center of the universe I can talk on behalf of others). P.S. some might not find that funny, but as the great philosopher Joker once said, “why so serious?”
2 Likes
How do you automate Syncro script updates when a change is pushed to a GitHub repo?
Once you’ve created the wrapper script in Syncro with the corresponding direct URL to the script in GitHub, you never have to touch it again in Syncro. There is a slight lag time when you update the script in GitHub (we believe this is due to one or more CDN in the middle), but it’s usually instant. Make your edit and commit it in GitHub, and on the next run of the corresponding wrapper in Syncro, the updated payload should be downloaded and run on the endpoint.
If you make changes to a script in GitHub, and you notice the old version still runs on endpoints when you run the corresponding wrapper entry in Syncro, give it ~30 minutes for the CDN to pick up the change. One way to tell would be to have a line at the top of the script in GitHub that you update - something like:
write-host “ | version | updated ”
Ex:
write-host “Printer Reset Script | Version 1.2 | Updated 11/4/25”
On the next run in Syncro, you should see that in the output, and if not, you know the CDN delivered the cached old version.
1 Like