Use deepseek for pr reviews - #7
Merged
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR switches the CI PR review workflow from ZAI to DeepSeek by replacing ZAI_API_KEY with DEEPSEEK_API_KEY in the GitHub Actions environment block. The change is correct: DEEPSEEK_API_KEY is the documented environment variable for DeepSeek authentication in pi, and the relay CLI resolves provider API keys through pi's standard AuthStorage mechanism. No secrets are exposed, no behavior changes beyond the provider switch, and the removed inline comments are preserved in the bundled README. Risk level: low.
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.
Moving to deepseek for pr reviews.
First deepseek pr review 🫡 🙏