docs(github): add rules for bounding git diff and log outputs#131
Merged
Conversation
spashii
approved these changes
Jul 1, 2026
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
2 participants
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.
What is this change?
This change adds a new section 'Bounding Git Diff and Log Outputs' to
src/capabilities/github.mddirecting Sam to avoid running unconstrained rawgit diffor log commands on large branches. It instructs Sam to check file sizes with--statfirst, restrict paths, and exclude massive generated files or schema JSON snapshots.What did Sam notice that led to this?
During today's early runs, session
9d21933a8efacrashed with a Vertex400 INVALID_ARGUMENTexception because it ran an unconstrainedgit diffon thesam/portal-prefillingbranch (which contains massive schema snapshots/sync JSONs). The 4.2MB diff output translated to ~1.2M tokens and overloaded the context window on the next turn. This PR prevents future session context overflows.Tier?
Tier 1 (capability prose).
Confidence?
High. This is a robust prose fix addressing a severe context window crash pattern.