npm run sync 09/25/2026 6:31 PM ET - #107
Merged
Merged
Conversation
report: changed=true changes=145 urgent=0 standings=unchanged rank-moves=0 merge=auto zones-unknown=0 standings-degraded=none
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 ESPN provider check found changes for the next snapshot. This PR proposes 145 fixture change records and 0 changed standings rows, including 0 rank moves. These update the app’s fixture or table information after publication.
Fixture changes: date changes (ET) (39); kickoff-time changes (36); kickoff-time confidence changes (70). Counts describe change records, not distinct matches.
No fixture changes were flagged time-sensitive by the sync rules.
If a reported change affects an open position, independently re-verify that fixture against primary sources (Step 0), then re-read the app after publication.
Fixtures and standings travel together as one snapshot. The workflow requests auto-merge, gated by required
verify; merging updates main, while the live app needs a successful Pages deployment. This PR proves neither human review, independent fixture verification, nor live delivery.Technical details
report: changed=true changes=145 urgent=0 standings=unchanged rank-moves=0 merge=auto zones-unknown=0 standings-degraded=nonemerge=auto/merge=holdare reporting signals, not merge gates;holdalso covers disappeared records and home/away reversals at any horizon.Recent change digest — entries reach main with change-bearing snapshots. Quiet checks add no entry; the digest is not evidence of human review.
Failed fixture/standings fetches or validation create no snapshot PR; investigate Actions diagnostics. A missing PR alone does not prove failure. Later merge or delivery failures can leave a PR or a merged snapshot behind.
Full sync output: