At work, I’ve seen my coworker set up this new cool tool called Rennovate which automatically scans your repository and opens PRs for updating dependencies. You control it through an online dashboard , or, and this is the part I found really cool, through the Github UI itself via (presumably) some fun webhook hacks. However, for this system to work properly, there needs to be some way of knowing if an opened PR is good to merge or not. I don’t really want to do the manual work of “check out an automatically opened PR” →\rightarrow → “make sure it works locally” →\rightarrow → “merge the PR and clean up local git” when I could have computers do that work for me! So I did a bunch of work to make computers do that work for me :] I borrowed heavily from the canonical Astro usecase, their own d…
At work, I’ve seen my coworker set up this new cool tool called Rennovate which automatically scans your repository and opens PRs for updating dependencies. You control it through an online dashboard , or, and this is the part I found really cool, through the Github UI itself via (presumably) some fun webhook hacks. However, for this system to work properly, there needs to be some way of knowing if an opened PR is good to merge or not. I don’t really want to do the manual work of “check out an automatically opened PR” →\rightarrow → “make sure it works locally” →\rightarrow → “merge the PR and clean up local git” when I could have computers do that work for me! So I did a bunch of work to make computers do that work for me :] I borrowed heavily from the canonical Astro usecase, their own documentation site , which seems to have been a pretty good template. Lots of “fun” making typescript and eslint and prettier all play nice together, but yep now it works now!! It correctly failed on the major version update of Astro, which I’ll need to do manually at some point, but that’s for another time yes.