fix: stop requeueing completed GitHub projections - #180
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Policy rebuilds repeatedly queued every repository until the entire summary backlog finished. Record the policy when its rebuild is queued, finish repository scopes independently, and retain pending connected-fork work and newer requests. Queue and completion updates are transactional; polling frequency and work attribution are unchanged.
Validation: 305 tests, typecheck, formatting/lint and both Knip modes pass. A local replay of 1,375 historical commits produced identical 334 work entries and 360 published snapshots; PostgreSQL response traffic for the full rebuild fell from 292.7 MB to 249.4 MB (14.8%). Local checks also covered stale requests, completion rollback and concurrent ingestion. The committed regression test requires no PostgreSQL service; no migrations or CI infrastructure changes.