Repository navigation
ci: validate Docker builds and tool installation - #27
Merged
Merged
Conversation
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
1 participant
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.
Add an independent Docker check for container and build-environment changes, excluding Markdown. It builds and caches a local Linux AMD64 image, installs PALM in a temporary container copy, and checks tool entry points. A manual full_pipeline option runs the minimal offline pipeline using installed binaries. All workflow actions use major-version tags.
Validation: actionlint, trigger-path review, documentation links, and patch whitespace passed. Automatic Docker checks, cache reuse, the manual full offline pipeline, and the full native CI suite passed. No model service was called.