ci: upgrade Gemini PR review model to gemini-2.5-flash-lite #8
@@ -22,6 +22,6 @@ jobs:
|
|||||||
GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
|
GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
|
||||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||||
with:
|
with:
|
||||||
model: gemini-1.5-flash-latest
|
model: gemini-2.5-flash-lite # Cheapest Gemini model - $0.10/1M input, $0.40/1M output
|
||||||
# You can add custom prompt instructions here if needed:
|
# You can add custom prompt instructions here if needed:
|
||||||
|
|
|||||||
# prompt: "You are a senior software engineer. Review this PR..."
|
# prompt: "You are a senior software engineer. Review this PR..."
|
||||||
|
|||||||
Reference in New Issue
Block a user
While the comment is informative about the cost, it's generally better practice to keep comments concise and focused on why a change was made, rather than what the change is or its specific pricing details. The pricing information could potentially become outdated. If the intent is to document the cost-effectiveness, consider a more general comment or a separate documentation file.