ci: send the PR base to TechEngine checks and stop tracking scores.jsonl - #294
Merged
Merged
Conversation
TechEngine #95 diffs against the PR's real base instead of a hard-coded origin/develop (release PRs reported no changes) or origin/main (develop PRs over-counted). Pass base_ref/base_sha from the validation relay, verify-report and /verify. scores.jsonl is a 43 MB generated cache that TechEngine no longer reads from git; untrack and ignore it. Refs #1
github-actions
Bot
added
data
5 tasks
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.
TechAPI side of GetTechAPI/TechEngine#95 (TechEngineBot full coverage), from the 2026-09-27 PR/issue audit.
request-engine-pr-validation,verify-reportandverify-commandnow sendbase_ref/base_shato TechEngine.origin/develop, so release PRs (develop→main, e.g. release: tablets, Surface laptops, benchmark backfill, SoC dates (2026-09-26) #292) reported "no data file changes".origin/main, so develop PRs over-counted (fix(data): resolve GPU conflicts against manufacturer specifications #290 changed 3 files but reported 2,127 records).scores.jsonluntracked and ignored: it's a 43.5 MB generated score cache that data(verify): verified promotions (2026-06-29) #95 no longer reads from git; at 12-category coverage it would near GitHub's 100 MB file limit.data/_verify/statecaches (URL, crossref, Wikipedia) stay tracked, because the network verifier relies on them to avoid re-fetching.git add data/in the engine workflows skips ignored files, so nothing breaks there.With #95, bot comments cover all 12 categories (191,797 records) instead of 8 categories, and the integrity gate covers everything instead of CPU/GPU only (3.4%).
Closes #1