fix: escape backticks in agent output for github-script

[sestinj]

Summary

• Fixes SyntaxError when agent output contains backticks (e.g., baseBranch)
• Uses environment variables instead of direct GitHub Actions expression interpolation in the Update Check Run step

Problem

When the Continue agent output contains backticks, they break the JavaScript template literal in the github-script action:

const output = `${{ steps.run.outputs.output }}`;
// If output contains `baseBranch`, it becomes:
const output = `Removes `baseBranch` prop...`;
//                      ^ breaks the template literal

This causes: SyntaxError: Unexpected identifier 'baseBranch'

Solution

Pass values through environment variables instead of direct interpolation:

env:
  AGENT_OUTPUT: ${{ steps.run.outputs.output }}
with:
  script: |
    const output = process.env.AGENT_OUTPUT || '';

This is a standard pattern for handling dynamic content in github-script actions.

Test plan

• Trigger the Continue Agents workflow on a PR where agent output contains backticks

🤖 Generated with Claude Code

---

Summary by cubic

Prevents SyntaxError in github-script when agent output includes backticks by passing values through environment variables instead of inline interpolation. Also ensures check run IDs are parsed correctly.

• Bug Fixes
  • Use env vars (AGENT_OUTPUT, AGENT_ERROR, AGENT_SUCCESS, CHECK_RUN_ID) in the Update Check Run step.
  • Read values via process.env and parseInt(CHECK_RUN_ID), avoiding template literals that break on backticks.

^{Written for commit 92bebf7. Summary will update on new commits.}

[continue-staging]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[continue]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ AI review failed. Please check the Continue API key and configuration.

Troubleshooting

• Verify the CONTINUE_API_KEY secret is set correctly
• Check that the organization and config path are valid
• Ensure the Continue service is accessible

---

[cubic-dev-ai]

No issues found across 1 file