What happened?
Both the Gemini Scheduled Issue Triage and Gemini Automated Issue Triage workflows are failing with an Argument list too long error. This occurs because the workflows load potentially huge JSON arrays or text of untriaged issues (which include issue bodies) directly into bash environment variables during their respective issue fetching and preparation steps.
What did you expect to happen?
The workflows should be able to safely fetch and process untriaged issues without exceeding the operating system's maximum environment variable size limits, enabling the Gemini issue analysis steps to process them successfully.
Client information
Client Information
Automated GitHub Actions environment.
Login information
GitHub Actions using a GitHub App token and GCP Workload Identity Federation.
Anything else we need to know?
The workflows are also encountering an "untrusted directory" error due to changes in how run-gemini-cli evaluates workspaces in headless mode.
What happened?
Both the
Gemini Scheduled Issue TriageandGemini Automated Issue Triageworkflows are failing with anArgument list too longerror. This occurs because the workflows load potentially huge JSON arrays or text of untriaged issues (which include issue bodies) directly into bash environment variables during their respective issue fetching and preparation steps.What did you expect to happen?
The workflows should be able to safely fetch and process untriaged issues without exceeding the operating system's maximum environment variable size limits, enabling the Gemini issue analysis steps to process them successfully.
Client information
Client Information
Automated GitHub Actions environment.
Login information
GitHub Actions using a GitHub App token and GCP Workload Identity Federation.
Anything else we need to know?
The workflows are also encountering an "untrusted directory" error due to changes in how
run-gemini-clievaluates workspaces in headless mode.