quality/workflows
SHA256
6
1
Fork 0
Code Issues Pull requests Projects Releases Packages Activity Actions

Improve documented way to use config (thanks @kparal)

Browse source 
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2026-04-28 10:46:28 -07:00
commit 1ad34ddd6c
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -27,10 +27,12 @@ You must define the `AICR_API_KEY` as a secret in your repository; it must be a
...
with:
pr: ${{ forgejo.event.pull_request.number }}
config: 'include_mr_summary: false\nai_model: gemini-3.1-flash-lite-preview'
config: |
include_mr_summary: false
ai_model: gemini-3.1-flash-lite-preview
...
```
The string is written out as `.ai_review/config.yml`, so it can contain any config directive ai-code-review supports. The string is written with printf, so newline characters are written out as newlines in the file. You can use this to change the AI provider away from Gemini if desired.
The string is written out as `.ai_review/config.yml`, so it can contain any config directive ai-code-review supports. The string is written with printf, so newlines are written out as newlines in the file. You can use this to change the AI provider away from Gemini if desired.
You can use other contexts, if you like, but if so, you may need to change how the pull request number is discovered and passed through, and you may want to put `remove_label: false` in the `with` block to disable the attempt to remove the `ai-review-please` label after the review is done. If used as above, the workflow will post a review any time a label named `ai-review-please` is applied to a pull request.