search

anti-work / shortest

Have AI write and update tests for you
https://shortest.com
MIT License
187 stars 21 forks source link

Way to test changes for green build before committing #34

Closed slavingia closed 1 month ago

slavingia commented 1 month ago

, or auto revert if the changes cause the build to fail, or open new PR with head branch as the feature branch

m2rads commented 1 month ago

I think building a custom test runner could solve this and open many more possibilities.

crabest commented 1 month ago

@m2rads can you elaborate more? I don't understand the "custom test runner".

m2rads commented 1 month ago

@crabest I'm basically referring to a server where its primary purpose is to execute tests and report the results. I am suggesting creating a custom test runner that would work similarly to how GitHub Actions runs tests, but with more flexibility and integration with Shortest.

slavingia commented 1 month ago

could also address this:

I'll probably look at this during the weekend. It's definitely possible but I'm fairly sure we would need to do polling in a vercel cron with a personal access token. Just have to be careful about rate limits.

I'm not sure we can reply to webhooks instantly without creating a bot, like the vercel one. But if we did that, then we'd have to have permissions to add it to every repo instead of being able to grab any and all PR's or issues on any repo, like we can now. The commits would also be from the bot instead of our own account.

revise.dev that Josh Pigford is working on takes the bot strategy in a similar product. So, to me, it seems like a core differentiator would be keeping it so the commits come from our own accounts so we can push changes anywhere

slavingia commented 1 month ago

Look at GitHub bots like dependabot etc, which people are already familiar with. It would be really cool to spin up a feature branch PR, and then once it's green, auto merge into the main branch