Repository navigation
gemini: pre-trust workspace in ~/.gemini/trustedFolders.json - #3629
Open
adelva1984 wants to merge 1 commit into
Open
adelva1984 wants to merge 1 commit into
adelva1984 wants to merge 1 commit into
Conversation
Pre-populate `~/.gemini/trustedFolders.json` with `TRUST_FOLDER` for `github.workspace` before invoking `run-gemini-cli` across `gemini-review.yaml`, `gemini-invoke.yaml`, and `gemini-plan-execute.yaml`. - In `gemini-review.yaml`, `google-github-actions/run-gemini-cli` (`v0.1.22`) only pipes a single `"Y"` to `gemini extensions install`, which gets consumed by the workspace-trust prompt in newer `gemini-cli` releases, leaving the extension/skill consent prompt hanging until the job times out. - In `gemini-invoke.yaml` and `gemini-plan-execute.yaml`, trusting the workspace ensures workspace `.gemini/settings.json` (`mcpServers.github` and `tools.core`) is loaded when folder trust is enforced in headless mode. Assisted-by: Jetski:Gemini
adelva1984
force-pushed
the
fix/gemini-review-trusted-folders
branch
from
November 18, 2026 21:54
781a3d3 to
dedad6f
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pre-populates
~/.gemini/trustedFolders.jsonwithTRUST_FOLDERforgithub.workspacebefore invokingrun-gemini-cliacross.github/workflows/gemini-review.yaml,.github/workflows/gemini-invoke.yaml, and.github/workflows/gemini-plan-execute.yaml.gemini-review.yaml,google-github-actions/run-gemini-cli(v0.1.22) only pipes a single"Y"togemini extensions install, which gets consumed by the workspace-trust prompt in newergemini-clireleases (0.68.0), leaving the extension/skill consent prompt hanging until the 15-minute job timeout.gemini-invoke.yamlandgemini-plan-execute.yaml, trusting the workspace ensures workspace.gemini/settings.json(mcpServers.githubandtools.core) is loaded when folder trust is enforced in headless mode.