docs(ingestion): correct GitHub repo skip condition to exact point IDs - #198
Open
detail-app[bot] wants to merge 1 commit into
Open
Conversation
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 GitHub ingestion doc listed the incremental-rerun skip condition as
"unchanged file + sufficient Qdrant points", describing the pre-0910f110
count-based contract (
hasSufficientStoredPointCoverageviacountPointsForUrl).The current contract requires the stored Qdrant point-ID set to match the expected
chunks exactly (
hasExactPointIdsForUrl); extra or missing points force a fullre-embed and stale-point cleanup.
Example: a developer debugging why an unchanged repo file gets re-embedded despite
Qdrant already holding many points for its URL would be misled by "sufficient" —
the real cause is leftover/superseded point IDs that break the exact-set match.
Sibling docs (docs/ingestion.md, docs/pipeline-commands.md) were already updated to
"exact Qdrant point IDs"; this aligns the GitHub ingestion doc with them.
Introduced by commit 0910f11 (@WilliamAGH, #192)
Doc Drift PRs can be configured here.