Repository navigation
fix: generate PaperViz container build inputs - #3
Merged
Merged
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 first container release failed because its fresh checkout lacked
web/src/ops.json, a ToolFactory build product that is intentionally untracked. Generate the container inputs before invoking Docker, matching the successful package and Pages jobs. Exclude local dependencies and environment files from the Docker context, document the local build prerequisite, and smoke-test the built image's CLI and web assets.Validation: reproduced a clean checkout, ran the published ToolFactory 0.1.2 build, confirmed the operations schema exists, and completed the locked web install and production build. ToolFactory drift check and whitespace checks pass. Runtime tests, release packaging and Pages passed in the previous run; the next dispatch verifies the actual Linux container build.