Skip to content

gemini-cli does not respond to the request #199

Closed

Description

@fujitatomoya

(I am not sure if this is the issue, could be mis-operation but could not find the good resource how to solve this situation.)

I just enabled gemini-cli github action on https://github.com/fujitatomoya/ros2_persist_parameter_server aligned with the procedure https://github.com/google-github-actions/run-gemini-cli?tab=readme-ov-file#quick-start.

but it does not seem that works as expected. gemini-cli does not respond the request, for example fujitatomoya/ros2_persist_parameter_server#37 (comment)

i guess that i maybe am missing something here.

Activity

  1. fujitatomoya commented on Aug 20, 2025

    @fujitatomoya
    Author

    it seems to be working against issues, fujitatomoya/ros2_persist_parameter_server#49 (comment) but PRs

  2. ArneTR commented on Aug 20, 2025

    @ArneTR

    I am also experiencing a similar issue where a trigger with @gemini-cli /review kicks off the workflow, but Gemini does not know what to do.

    When looking into the GitHUb Acitons logs it just says "Ready to go. What can I help you with?"

    Example: https://github.com/green-coding-solutions/green-metrics-tool/actions/runs/17092479519/job/48469133846

    Image
  3. added
    kind/bugSomething isn't working
    priority/p1Important and should be addressed in the near term
    on Aug 20, 2025
  4. Cody-G-G commented on Aug 20, 2025

    @Cody-G-G

    having the same issue as @ArneTR above

  5. fujitatomoya commented on Aug 20, 2025

    @fujitatomoya
    Author

    hmmm, thanks for the information guys. at least i am not the only one who is facing this unstable behavior, that i can know that. i guess that is because this is still beta...

  6. added this to the v0.1.12 milestone on Aug 21, 2025
  7. jerop commented on Aug 25, 2025

    @jerop
    Contributor

    There's a quality issue in Gemini CLI generally since last week that the team is actively working on - google-gemini/gemini-cli#6474

  8. modified the milestones: v0.1.12, v0.1.13 on Aug 25, 2025
  9. fujitatomoya commented on Aug 26, 2025

    @fujitatomoya
    Author

    @jerop thanks for letting me know!

  10. jfyne commented on Sep 5, 2025

    @jfyne

    Also seeing this for reviews:

    Warning: Unexpected input(s) 'google_api_key', 'gemini_debug', valid inputs are ['prompt', 'settings', 'gemini_api_key', 'gcp_project_id', 'gcp_location', 'gcp_workload_identity_provider', 'gcp_service_account', 'use_vertex_ai', 'use_gemini_code_assist', 'gemini_cli_version']
    Run google-github-actions/run-gemini-cli@v0
    Run mkdir -p .gemini/
    Run google-github-actions/auth@v2
    Created credentials file at "/home/runner/work/hmm/hmm/gha-creds-53f3d8e6c434ebb6.json"
    Run set -euo pipefail
    Unable to find image 'otel/opentelemetry-collector-contrib:0.128.0' locally
    0.128.0: Pulling from otel/opentelemetry-collector-contrib
    516cf8f3105f: Pulling fs layer
    22bbe0bff504: Pulling fs layer
    85e6603fa2d3: Pulling fs layer
    516cf8f3105f: Verifying Checksum
    516cf8f3105f: Download complete
    85e6603fa2d3: Verifying Checksum
    85e6603fa2d3: Download complete
    516cf8f3105f: Pull complete
    22bbe0bff504: Download complete
    22bbe0bff504: Pull complete
    85e6603fa2d3: Pull complete
    Digest: sha256:1ab0baba0ee3695d823c46653d8a6e8894896e668ce8bd7ebe002e948d827bc7
    Status: Downloaded newer image for otel/opentelemetry-collector-contrib:0.128.0
    3b82cee38e5bc1186dea9a7860ba3c771f7ea2fd79eb8a726300fbc635a09d6e
    Run set -euo pipefail
    Installing Gemini CLI from npm: @google/gemini-cli@latest
    Verifying installation:
    0.3.2
    Run set -euo pipefail
    Gemini response
      Understood. I am ready to proceed with the code review as instructed.
    
  11. modified the milestones: v0.1.13, v0.1.14 on Sep 16, 2025
  12. modified the milestones: v0.1.14, v0.1.15 on Oct 23, 2025
  13. removed this from the v0.1.15 milestone on Nov 18, 2025
  14. self-assigned this
    on Nov 20, 2025
  15. MJjainam commented on Dec 1, 2025

    @MJjainam
    Contributor

    This should be fixed with the latest release @fujitatomoya

  16. MJjainam commented on Dec 2, 2025

    @MJjainam
    Contributor

    Please re-open if this still persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/qualityTracks quality issueskind/bugSomething isn't workingpriority/p1Important and should be addressed in the near term

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions