From a3b7f5d5e1cdb2a4b8a0232f3e1641d753f7c1bc Mon Sep 17 00:00:00 2001 From: cocosheng-g Date: Tue, 3 Feb 2026 20:34:42 -0500 Subject: [PATCH] fix(dedup): clarify tool usage for logging output --- .github/workflows/gemini-automated-issue-dedup.yml | 2 +- .github/workflows/gemini-scheduled-issue-dedup.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/gemini-automated-issue-dedup.yml b/.github/workflows/gemini-automated-issue-dedup.yml index 0fe02b5530..f1c7116c63 100644 --- a/.github/workflows/gemini-automated-issue-dedup.yml +++ b/.github/workflows/gemini-automated-issue-dedup.yml @@ -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 --json title,body,comments` to fetch its content. diff --git a/.github/workflows/gemini-scheduled-issue-dedup.yml b/.github/workflows/gemini-scheduled-issue-dedup.yml index 46a6f4628b..d3f1488844 100644 --- a/.github/workflows/gemini-scheduled-issue-dedup.yml +++ b/.github/workflows/gemini-scheduled-issue-dedup.yml @@ -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