Skip to content

Raise max-patch-size for Deep Report repo-memory push - #54029

Merged
pelikhan merged 2 commits into
mainfrom
copilot/aw-failures-raise-max-patch-size
Aug 19, 2026
Merged

Raise max-patch-size for Deep Report repo-memory push#54029
pelikhan merged 2 commits into
mainfrom
copilot/aw-failures-raise-max-patch-size

Conversation

CopilotAI commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Deep Report's push_repo_memory step hard-fails when the staged diff exceeds max-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: set max-patch-size: 51200 (50KB) on the repo-memory tool 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 into GH_AW_MEMORY_CONSTRAINTS, GH_AW_SAFE_OUTPUTS_CONFIG, and the push_repo_memory job's MAX_PATCH_SIZE env var.
tools:
repo-memory:
branch-name: memory/deep-reportdescription: "Long-term insights, patterns, and trend data"file-glob: ["*.md", "*.json"]max-file-size: 1048576# 1MBmax-patch-size: 51200# 50KB - default (10KB) is too small for a full analysis cycle's diff

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
CopilotAI changed the title [WIP] Raise max-patch-size for Deep Report's repo-memoryRaise max-patch-size for Deep Report repo-memory pushAug 19, 2026
CopilotAI requested a review from pelikhanAugust 19, 2026 15:02
@github-actions

Copy link
Copy Markdown
Contributor

PR Triage

Category: chore · Risk: low · Score: 40/100 (impact 15 + urgency 15 + quality 10)
Recommended action:fast_track

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.

Generated by 🔧 PR Triage Agent · auto · 90.2 AIC · ⌖ 2.82 AIC · ⊞ 8.3K ·

@pelikhan
pelikhan marked this pull request as ready for review August 19, 2026 23:49
CopilotAI balanced review requested due to automatic review settings August 19, 2026 23:49
@pelikhan
pelikhan merged commit 5d5e0af into mainAug 19, 2026
1 check passed
@pelikhan
pelikhan deleted the copilot/aw-failures-raise-max-patch-size branch August 19, 2026 23:49

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Raises Deep Report’s repo-memory patch limit to prevent legitimate analysis updates from being discarded.

Changes:

  • Increases max-patch-size from 10 KB to 50 KB.
  • Regenerates the compiled workflow with the new limit.
Show a summary per file
FileDescription
.github/workflows/deep-report.mdConfigures the 50 KB patch limit.
.github/workflows/deep-report.lock.ymlPropagates 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

@github-actions

Copy link
Copy Markdown
Contributor

🎉 This pull request is included in a new release.

Release: v0.87.2

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[aw-failures] [P1] Deep Report push_repo_memory drops generated content when diff exceeds max-patch-size

3 participants

@pelikhan