Problem
In the claude-review.yml workflow (PR Reviews with Claude Code), the createInlineComment.sh script fails silently on every PR because allowed-rules.txt is missing at the "Post code review results" step.
The "Extract allowed rules" step runs earlier and writes the file to $GITHUB_WORKSPACE/.claude/allowed-rules.txt, but the claude-code-action step runs between those two steps and modifies the workspace, removing the untracked file. As a result, zero reviewer inline comments have been posted since the structured output workflow was deployed. The error is swallowed by || true, so the failure is invisible.
Solution
Store allowed-rules.txt in $RUNNER_TEMP instead of $GITHUB_WORKSPACE. $RUNNER_TEMP persists across all job steps within a runner and is unaffected by git operations or workspace modifications. Additionally, make the ALLOWED_RULES_FILE path in createInlineComment.sh overridable via an environment variable with a fallback to the old path for backward compatibility.
Fix PR: #87803
Issue Owner
Current Issue Owner: @kacper-mikolajczak
Problem
In the
claude-review.ymlworkflow (PR Reviews with Claude Code), thecreateInlineComment.shscript fails silently on every PR becauseallowed-rules.txtis missing at the "Post code review results" step.The "Extract allowed rules" step runs earlier and writes the file to
$GITHUB_WORKSPACE/.claude/allowed-rules.txt, but theclaude-code-actionstep runs between those two steps and modifies the workspace, removing the untracked file. As a result, zero reviewer inline comments have been posted since the structured output workflow was deployed. The error is swallowed by|| true, so the failure is invisible.Solution
Store
allowed-rules.txtin$RUNNER_TEMPinstead of$GITHUB_WORKSPACE.$RUNNER_TEMPpersists across all job steps within a runner and is unaffected by git operations or workspace modifications. Additionally, make theALLOWED_RULES_FILEpath increateInlineComment.shoverridable via an environment variable with a fallback to the old path for backward compatibility.Fix PR: #87803
Issue Owner
Current Issue Owner: @kacper-mikolajczak