Pass bridge source token to Workbench smoke build - #377
Conversation
📝 WalkthroughWalkthroughA preflight bash step is added to the smoke workflow that checks for ChangesGH_TOKEN Validation and Bridge Source Token Wiring
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/workbench-functional-smoke.yml:
- Around line 123-126: The "Build unpacked app only" step's env section only
forwards EVAOS_DESKTOP_BRIDGE_SOURCE_TOKEN but does not export GH_TOKEN, which
is required by the upstream prepare-aioncore.js script. Add GH_TOKEN to the env
section of the build step by mapping it from secrets.GH_TOKEN, similar to how
EVAOS_DESKTOP_BRIDGE_SOURCE_TOKEN is already configured, to satisfy the
authentication contract expected by the shared build script.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 1eccddf6-8856-4005-b86a-40588757c383
📒 Files selected for processing (1)
.github/workflows/workbench-functional-smoke.yml
📜 Review details
⏰ Context from checks skipped due to timeout. (6)
- GitHub Check: Build Test (macos-arm64)
- GitHub Check: Build Test (windows-arm64)
- GitHub Check: Build Test (linux)
- GitHub Check: Build Test (windows-x64)
- GitHub Check: Unit Tests (windows-2022)
- GitHub Check: Build Test (macos-x64)
🔇 Additional comments (1)
.github/workflows/workbench-functional-smoke.yml (1)
112-122: LGTM!
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/workbench-functional-smoke.yml (1)
123-127: 🧹 Nitpick | 🔵 TrivialAdd
GITHUB_TOKENto env block as defensive fallback.The build script (
prepare-aioncore.js) explicitly checks bothGH_TOKENandGITHUB_TOKEN(in that order). While the primary path usesgh apiwhich honoursGH_TOKENautomatically, a curl fallback exists for scenarios whereghis unavailable. AddingGITHUB_TOKENensures the fallback path works without relying on primary path success.Diff
- name: Build unpacked app only shell: bash env: EVAOS_DESKTOP_BRIDGE_SOURCE_TOKEN: ${{ secrets.GH_TOKEN }} GH_TOKEN: ${{ secrets.GH_TOKEN }} + GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/workbench-functional-smoke.yml around lines 123 - 127, Add GITHUB_TOKEN to the env block in the "Build unpacked app only" step by including GITHUB_TOKEN: ${{ secrets.GH_TOKEN }} alongside the existing GH_TOKEN and EVAOS_DESKTOP_BRIDGE_SOURCE_TOKEN environment variables. This ensures that the curl fallback path in the prepare-aioncore.js script has access to authentication credentials when the primary gh command path is unavailable.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In @.github/workflows/workbench-functional-smoke.yml:
- Around line 123-127: Add GITHUB_TOKEN to the env block in the "Build unpacked
app only" step by including GITHUB_TOKEN: ${{ secrets.GH_TOKEN }} alongside the
existing GH_TOKEN and EVAOS_DESKTOP_BRIDGE_SOURCE_TOKEN environment variables.
This ensures that the curl fallback path in the prepare-aioncore.js script has
access to authentication credentials when the primary gh command path is
unavailable.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 9e30747a-b4dd-4765-b11e-59991259972e
📒 Files selected for processing (1)
.github/workflows/workbench-functional-smoke.yml
📜 Review details
⏰ Context from checks skipped due to timeout. (10)
- GitHub Check: Build Test (windows-arm64)
- GitHub Check: Build Test (macos-arm64)
- GitHub Check: Build Test (linux)
- GitHub Check: Unit Tests (ubuntu-latest)
- GitHub Check: Build Test (windows-x64)
- GitHub Check: Unit Tests (windows-2022)
- GitHub Check: Code Quality
- GitHub Check: Unit Tests (macos-14)
- GitHub Check: Coverage Test
- GitHub Check: Build Test (macos-x64)
🔇 Additional comments (1)
.github/workflows/workbench-functional-smoke.yml (1)
112-122: LGTM!
Summary
Validation
actionlint .github/workflows/workbench-functional-smoke.ymlBUN_INSTALL_CACHE_DIR=/Volumes/LEXAR/Codex/.cache/bun bunx oxfmt@0.41.0 --check .github/workflows/workbench-functional-smoke.ymlgit diff --checkNotes
This keeps the public release pipeline out of the debugging loop. The next proof step is to rerun
Workbench Functional Smokeagainstevaos/beta-rc-20260612and use that staging artifact for Mac pairing proof.Summary by CodeRabbit