[codex] Cache idsdb artifacts in CI#27
Merged
Merged
Conversation
Restore generated idsdb and idsdb-fts5 database artifacts alongside input-hash stamps so unchanged inputs can skip rebuilds on fresh GitHub Actions runners. Related: #23 Generated-by: Codex/GPT-5.4
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.
Summary
idsdbandidsdb-fts5SQLite artifacts plus their input-hash stamp files.Why
Full CI runs currently rebuild
idsdbwhen a fresh runner has noidsfind.dbor.idsdb.input.sha256, even if the PR did not touch DB inputs. Restoring those artifacts lets the existingpreparehash checks printinputs unchanged, skipping rebuildwhen the cache is valid.Validation
.github/workflows/validate.ymland.github/workflows/release.ymlwith Ruby YAML.Related: #23