Repository navigation
Improve build progress and completion actions - #157
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bdd92aa207
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Build Map previously closed its progress notification without a completion message or a way to find the output. Successful builds now show the output folder with Open Build Folder and Show Log actions. Failed and canceled builds do not show success, and dismissing the notification does not delay command completion.
The shared Build/Run progress handler also forwards compiler percentages as bounded VS Code progress increments when available. Build already used the same progress wiring as Run; this change preserves that behavior.
Validation: TypeScript typecheck, npm run lint, npm test, and git diff --check passed. Regression coverage checks progress updates, failure/cancellation handling, completion actions, and opening the server workspace's _build folder when the input map lives elsewhere. Native File Explorer launch was not tested interactively.