ci: add gemini ai pr review action #3
@@ -0,0 +1,27 @@
|
||||
name: "Gemini AI PR Review"
|
||||
|
|
||||
|
||||
on:
|
||||
pull_request:
|
||||
types: [opened, synchronize, reopened]
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
review:
|
||||
name: "Code Review"
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout Repository
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Gemini AI Review
|
||||
uses: petarzarkov/gemini-code-review-action@v1.0.4 # Pinned version for stability
|
||||
env:
|
||||
GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
with:
|
||||
model: gemini-1.5-flash-latest
|
||||
# You can add custom prompt instructions here if needed:
|
||||
# prompt: "You are a senior software engineer. Review this PR..."
|
||||
Reference in New Issue
Block a user
It's generally recommended to pin the version of an action to a specific commit hash or a major version tag (e.g.,
@v1) rather than using@latest. This prevents unexpected breaking changes if the action is updated in a way that's not backward compatible.Consider changing
@latestto a more specific version, like@v1.0.0or a commit SHA, to ensure the workflow remains stable.