Closed OAGr closed 1 week ago
vercel[bot]
commented
2 weeks ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated (UTC) |
|---|---|---|---|
| quri-hub | ✅ Ready (Inspect) | Visit Preview | Nov 13, 2024 0:31am |
| squiggle-website | ✅ Ready (Inspect) | Visit Preview | Nov 13, 2024 0:31am |
changeset-bot[bot]
commented
2 weeks ago Latest commit: 90f205f924057a63d3f4a17ee3fa0b7d215f121e
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Thinking through this:
We have steps for
GenerateCode,FixCodeUntilItRuns,AdjustToFeedback,MatchStyleGuide.The order is
GenerateCode-->FixCodeUntilItRuns-->AdjustToFeedback-->MatchStyleGuide.At each of the latter 3 stages, if the code changes, it should go back to a pipeline to make sure that the code runs, then run it through
AdjustToFeedback.In addition, we'd ideally have rules like:
FixCodeUntilItRunshas to run more than ~4 times, it rolls back to the last [working version, or makes a newGenerateCodeor similar]We have templates for
CreateSquiggleandFixSquiggle.We want
CreateSquiggleWorkflowTemplate to go through all the steps. We wantFixSquiggleto only doFixCodeUntilItRunsandAdjustToFeedback. We will soon want a"StyleSquiggle"WorkflowTemplate that just does theMatchStyleGuidestep, maybe configured to be very likely to actually run (as opposed to rejecting, saying that the style guide is already good enough).Claude made this diagram. I think this diagram has some problems, but I think it's not too bad at giving a rough idea for how this could work.