Skip to content

Commit fbd8a09

Browse files
committed
readme(GHA): Add links to run-gemini-cli and its configuration
1 parent b78b400 commit fbd8a09

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -39,23 +39,23 @@ By default, the `/security:analyze` command determines the scope of the analysis
3939

4040
## GitHub Integration
4141

42-
### I already use run-gemini-cli workflows in my repository:
42+
### I already use [run-gemini-cli](https://github.com/google-github-actions/run-gemini-cli) workflows in my repository:
4343

4444
* Replace your existing `gemini-review.yml` with this [updated workflow](https://github.com/gemini-cli-extensions/security/blob/main/.github/workflows/gemini-review.yml), which includes the new Security Analysis step.
4545

46-
### I don't use run-gemini-cli workflows in my repository yet:
46+
### I don't use [run-gemini-cli](https://github.com/google-github-actions/run-gemini-cli) workflows in my repository yet:
4747

4848
1. Integrate the Gemini CLI Security Extension into your GitHub workflow to analyze incoming code:
4949

50-
1. Follow Steps 1-3 in this [Quick Start](https://github.com/google-github-actions/run-gemini-cli?tab=readme-ov-file#quick-start).
50+
2. Follow Steps 1-3 in this [Quick Start](https://github.com/google-github-actions/run-gemini-cli?tab=readme-ov-file#quick-start).
5151

52-
1. Create a `.github/workflows` directory in your repository's root (if it doesn't already exist).
52+
3. Create a `.github/workflows` directory in your repository's root (if it doesn't already exist).
5353

54-
1. Copy this [Example Workflow](https://github.com/gemini-cli-extensions/security/blob/main/.github/workflows/gemini-review.yml) into the `.github/workflows` directory.
54+
4. Copy this [Example Workflow](https://github.com/gemini-cli-extensions/security/blob/main/.github/workflows/gemini-review.yml) into the `.github/workflows` directory. See the run-gemini-cli [configuration](https://github.com/google-github-actions/run-gemini-cli?tab=readme-ov-file#configuration) to make changes to the workflow.
5555

56-
1. Ensure the new workflow file is committed and pushed to GitHub.
56+
5. Ensure the new workflow file is committed and pushed to GitHub.
5757

58-
1. Open a new pull request, or comment `@gemini-cli /review` on an existing PR, to run the Gemini CLI Code Review along with Security Analysis.
58+
6. Open a new pull request, or comment `@gemini-cli /review` on an existing PR, to run the Gemini CLI Code Review along with Security Analysis.
5959

6060
## Benchmark
6161

commands/security/analyze-github-pr.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ After completing these two initial tasks, continue executing the dynamically gen
132132
133133
3.1 **Create Pending Review:** Call `create_pending_pull_request_review`. Ignore errors like "can only have one pending review per pull request" and proceed to the next step.
134134
135-
3.2 **Add Comments and Suggestions:** For each formulated review comment, make the mcp call `add_comment_to_pending_review`.
135+
3.2 **Add Comments and Suggestions:** For each formulated review comment, call `add_comment_to_pending_review`.
136136
137137
2a. When there is a code suggestion (preferred), structure the comment payload using this exact template:
138138

0 commit comments

Comments
 (0)