sync branches, improve environment variable handling, the AI call process and the response format schema.#9
Merged
Droid-An merged 38 commits intoCodeYourFuture:mainfrom Mar 9, 2026
Conversation
… function to test ai review in isolation
implemented post inline comments feature
…trigger only when 'needs review' is set, update scripts
Tag listener
Droid-An
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves environment variable handling, the AI call process, and the response format schema.
The JSON schema is now generated from the Zod validation schema, making the Zod schema the single source of truth. This means that if the AI response format needs to change, it only needs to be updated in one place.
This PR also adds retry functionality to handle cases where the AI response is invalid.
Additionally, I introduced new logic for environment variable configuration. In production, the GitHub private key must now be provided directly as an environment variable. In development, the key is read from a file, and the path to that file is stored in the environment variable instead.