Update documentation workflows with workspace trust#26150
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Hi @g-samroberts, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
|
Size Change: -4 B (0%) Total Size: 33.9 MB
ℹ️ View Unchanged
|
Summary
This PR addresses a recent CI failure affecting automated documentation tasks (
docs-audit.ymlandrelease-notes.ymlfor generating changelogs). The Gemini CLI workflows were failing with an untrusted directory error.Fixes #26151
Changes
GEMINI_CLI_TRUST_WORKSPACE: trueenvironment variable to thegoogle-github-actions/run-gemini-cliaction step in both.github/workflows/docs-audit.ymland.github/workflows/release-notes.yml. This explicitly bypasses the untrusted workspace block for headless environments, allowing the automated documentation and changelog generation to proceed normally.Validation
GEMINI_CLI_TRUST_WORKSPACEconvention matches the usage in existing successful workflows (likeci.yml).