|
|
|
|
|
|
by ElijahLynn
2 days ago
|
|
|
Definitely going to look into this! I just built something pretty much in the same vein of this with Claude over the past 2 months. It's a custom deployment system that uses work trees and each work tree has to to run end-to-end tests (Playright, Supabase, Astro) and other tests and create a stamp based on the contents of the entire tree. And then if another work tree has the same digest that matches the stamp then it can bypass the tests. So nothing can land on main without tests passing. Which is all in in enforced with a pre-push hook that checks the digest. Then once it's on main it is deployed to Dev and then from there it can be promoted to prod. I like the idea of just having one branch and the work trees funnel into it. But definitely going to have my setup analyze this and see what can be improved with it or if I should just throw out mine and use that one. |
|
|