MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-03-12 15:10:59 -07:00
Code Issues Packages Projects Releases Wiki Activity

fix(dedup): clarify tool usage for logging output

Browse Source
This commit is contained in:
cocosheng-g
2026-02-03 20:34:42 -05:00
parent d9a0e9b9c5
commit a3b7f5d5e1
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/gemini-automated-issue-dedup.yml vendored
View File

@@ -123,7 +123,7 @@ jobs:
- The repository is ${{ github.repository }} and the issue number is ${{ github.event.issue.number }}.
- Use the `duplicates` tool with the `repo` and `issue_number` to find potential duplicates for the current issue. Do not use the `threshold` parameter.
- If no duplicates are found, you are done.
- Print the JSON output from the `duplicates` tool to the logs.
- Use the `echo` command to print the JSON output from the `duplicates` tool to the logs.
2. **Refine Duplicates List (if necessary):**
- If the `duplicates` tool returns between 1 and 14 results, you must refine the list.
- For each potential duplicate issue, run `gh issue view <issue-number> --json title,body,comments` to fetch its content.

2
.github/workflows/gemini-scheduled-issue-dedup.yml vendored
View File

@@ -106,7 +106,7 @@ jobs:
1. **Extract Repository Information:** The repository is ${{ github.repository }}.
2. **Refresh Embeddings:** Call the `refresh` tool with the correct `repo`. Do not use the `force` parameter.
3. **Log Output:** Print the JSON output from the `refresh` tool to the logs.
3. **Log Output:** Use the `echo` command to print the JSON output from the `refresh` tool to the logs.
## Guidelines