Fix portfolio-analyst workflow: use local binary instead of CLI extension #14630
+3
−3
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.
The portfolio-analyst workflow failed at step 14 with
unknown command "aw" for "gh". The workflow invokedgh aw logsin a manual step before the agent job runs, but the CLI extension installation step is conditional and was skipped.Changes
gh aw logsto./gh-aw logsin.github/workflows/portfolio-analyst.md.github/workflows/portfolio-analyst.lock.ymlTechnical Details
The gh-aw binary is built and copied to
./gh-awduring the "Build gh-aw CLI" step, making it available for manual steps without requiring the CLI extension. This pattern is already used insafe-output-health.md.Before:
After:
Pattern
For workflows needing gh-aw commands in pre-processing steps:
./gh-aw(local binary, always available)gh aw(CLI extension, conditionally installed)agentic-workflows:tool (MCP server for AI agent, not shell commands)Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.