DEV3-5474 fix: move TABNINE_CLI_TRUST_WORKSPACE to the agent invocation step#36
Merged
Merged
Conversation
The env var was set on the `Authenticate GitHub CLI` step, which only
runs `gh auth login` — not the tabnine CLI. Step-level `env:` does not
flow to later steps in a composite action, so by the time the actual
`~/.local/bin/tabnine` invocation step ran, `TABNINE_CLI_TRUST_WORKSPACE`
was unset and the CLI exited with code 55:
> Tabnine CLI is not running in a trusted directory. To proceed, either
> use `--skip-trust`, set the `TABNINE_CLI_TRUST_WORKSPACE=true`
> environment variable, or trust this directory in interactive mode.
Move the env var onto the `${{ inputs.step_name }}` step (the one that
actually runs the CLI) and drop it from the gh auth step where it had
no effect.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
yonidavidson
approved these changes
May 15, 2026
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.
Summary
TABNINE_CLI_TRUST_WORKSPACE: "true"env added in DEV3-5474: add TABNINE_CLI_TRUST_WORKSPACE=true env var #35 was placed on theAuthenticate GitHub CLIstep, which only runsgh auth login— not the tabnine CLI.env:does not flow to subsequent steps in a composite action, so by the time the actual~/.local/bin/tabnineinvocation step ran, the env var was unset and the CLI exited with code 55:@mainafter the tabnine-clifeat(cli): secure .env loading and enforce workspace trust in headless modechange.Fix
Move the env var onto the
${{ inputs.step_name }}step (the one that actually invokes the CLI), and drop it from the gh auth step where it had no effect.Test plan
🤖 Generated with Claude Code