Repository navigation
fix: retain community verification inputs in site deployment - #122
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
fix
the first production build after #121 stopped before publication: the sparse checkout omitted scripts/build-ft2-linux.sh, which bundle verification reads for the pinned FT2 commit.
the contributor job on the previous head hit its 15-minute checkout timeout before any tests started. the source-only layout removes that unrelated artifact download rather than increasing timeouts or weakening the gate.
verification
no scoring, run evidence, ranking rules or live data changed. this fixes build and test inputs, not the validator.