What changed is answered from git history - #190
Merged
Merged
Conversation
The file index has no date on anything, so "the latest changes" ranked a month-old measurement write-up over 33 commits of the last two days. The poller now records each branch's first-parent history beside the file index (commits + commits_fts, BACKEND_HISTORY_DEPTH on a full run, the last_sha..head range on a poll). The understanding step reads a changes intent with a day window and a topic; such a turn skips search, routing and gathering and answers from the commits of the window, grouped per repository, never carded. Commits are sources and citations of their own kind, opened in a commit view whose touched paths open the file viewer; the share page gets the same view through its own endpoint. Author is stored and never served. A window with no commit is a templated answer.
…UTC, Show on a merge tested
…ipped, prompt bounded Review findings: an incremental append left a rebased or force-pushed branch answering both versions of a change, and a full re-index renumbered every row under the turns citing it; Sync inserts what is missing by sha, keeps what is held, and drops what the branch no longer has. Trailer lines named people in a body that reaches the answer and a public page. A root or vendor commit could exceed the context; body and path list are cut. Show runs --no-renames so a renamed path stays openable. since_days reads a quoted number, and the changes prompt block needs a window, not only the intent, so a pipeline without the lane never calls chunks commits.
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.
"Summarize the latest changes" answered from a month-old measurement write-up while 33 commits had landed in two days: the file index has no date on anything, so "latest" is a semantic match on documents that narrate changes.
What changed:
commits+commits_fts,BACKEND_HISTORY_DEPTHdeep, default 500).history.Synckeeps held rows by sha and drops what the branch no longer has, so a rebase or force-push leaves neither stale nor duplicate changes and a full re-index never orphans a cited commit. Snapshots record none.changesintent with a day window (default 14, capped 365, applied by the pipeline) and an optional topic. Such a turn skips search, routing and gathering and answers from the window's commits, grouped per repository, never carded; a topic filters through the keyword ladder's widest rung over subject, body and paths. Zero commits is a templated answer, no model call.message_sources.commit_idso a re-explain reads them back. A commit chip opens a commit view (message, date, touched files with line counts); a touched file opens the source viewer whole at its indexed commit. The share page gets the same view through/api/shares/{token}/commit, cited commits only.Signed-off-by,Co-authored-by) are stripped from the body. The prompt bounds each commit to 1500 runes of body and 30 paths.Deploy notes: migration 0028 forces a full re-index of every repository (the embedding cache makes it cheap); new optional
BACKEND_HISTORY_DEPTH.Not measured: the understanding prompt gained the
changesintent and two fields. The flow answers harness could not run here (no.env, corpus gone). The risk to check is an ordinary "how does X work" question read aschanges, which would skip the code search. Follow-ups: the measurement, and tag ranges ("what changed between 1.5.1 and 1.5.2").