Uh oh!
There was an error while loading. Please reload this page.
Raise max-patch-size for Deep Report repo-memory push - #54029
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
PR TriageCategory: chore · Risk: low · Score: 40/100 (impact 15 + urgency 15 + quality 10) Small config fix preventing silent data loss in Deep Report memory push; low risk, high value once undrafted. Automated triage — see run report for full details.
|
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Pull request overview
Raises Deep Report’s repo-memory patch limit to prevent legitimate analysis updates from being discarded.
Changes:
- Increases
max-patch-sizefrom 10 KB to 50 KB. - Regenerates the compiled workflow with the new limit.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/deep-report.md | Configures the 50 KB patch limit. |
.github/workflows/deep-report.lock.yml | Propagates the limit into generated runtime configuration. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Balanced
🎉 This pull request is included in a new release. Release: |
Deep Report's
push_repo_memorystep hard-fails when the staged diff exceedsmax-patch-size, silently dropping all staged file updates rather than just delaying them. A normal analysis cycle produced a ~13KB diff across 6 legitimately-updated repo-memory files, exceeding the framework default of 10KB (10240 bytes) by a small margin and losing the entire cycle's output.Changes
.github/workflows/deep-report.md: setmax-patch-size: 51200(50KB) on therepo-memorytool config, replacing the implicit 10KB default. Matches the value already used by comparable meta-analysis workflows (agent-performance-analyzer.md,workflow-health-manager.md,agentic-token-audit.md,agentic-token-optimizer.md), giving ~4x headroom over the observed diff size while still guarding against genuinely anomalous bulk diffs (hard cap remains 1MB)..github/workflows/deep-report.lock.yml: regenerated via the compiler to propagate the new limit intoGH_AW_MEMORY_CONSTRAINTS,GH_AW_SAFE_OUTPUTS_CONFIG, and thepush_repo_memoryjob'sMAX_PATCH_SIZEenv var.