Skip to content

Increase max-patch-size for LabelOps PR Maintenance workflow - #19726

Merged
T-Gro merged 4 commits into
mainfrom
copilot/aw-fix-patch-size-exceeded
May 18, 2026
Merged

Increase max-patch-size for LabelOps PR Maintenance workflow#19726
T-Gro merged 4 commits into
mainfrom
copilot/aw-fix-patch-size-exceeded

Conversation

CopilotAI commented May 13, 2026

Copy link
Copy Markdown
Contributor

LabelOps failed on PR #15107 because the patch from resolving .bsl merge conflicts was 9788 KB, exceeding the default 1024 KB limit. Baseline files routinely produce multi-MB diffs — the default cap is not meaningful for this workflow.

  • Set max-patch-size: 10240 (10 MB, compiler maximum) under safe-outputs in labelops-pr-maintenance.md
  • Recompiled lock file via gh aw compile
safe-outputs:
max-patch-size: 10240push-to-pull-request-branch:
target: "*"max: 5protected-files: fallback-to-issue

LabelOps resolving merge conflicts in .bsl baseline files can produce
patches of many megabytes. The default 1024 KB limit is too restrictive.
Set to maximum allowed value of 10240 KB (10 MB).
Fixes#18204
Agent-Logs-Url: https://github.com/dotnet/fsharp/sessions/2ab60227-7344-4950-a54e-ce17e8c45c90
Co-authored-by: T-Gro <46543583+T-Gro@users.noreply.github.com>
CopilotAI changed the title [WIP] Fix patch size exceeded error in PR maintenanceIncrease max-patch-size for LabelOps PR Maintenance workflowMay 13, 2026
CopilotAI requested a review from T-GroMay 13, 2026 09:09
@github-actionsgithub-actionsBot added the AI-Tooling-Check-Bypassed Tooling check: non-fork PR, not diff-analyzed label May 13, 2026
@github-actions

This comment has been minimized.

@T-Gro
T-Gro marked this pull request as ready for review May 14, 2026 09:58
@T-Gro
T-Gro requested a review from a team as a code ownerMay 14, 2026 09:58
@T-Gro
T-Gro requested a review from abonieMay 14, 2026 09:59
@github-actions

Copy link
Copy Markdown
Contributor

✅ No release notes required

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Tooling Safety Check — Bypassed (non-fork)

(scanned-sha)6021d9b33497b2e589293ea00be1a24df9eab925(/scanned-sha)

Generated by PR Tooling Safety Check · ● 1.5M ·

@T-GroT-Gro added the AI-Auto-Resolve-Conflicts Opt-in: LabelOps merges main into this PR and resolves conflicts every 3h label May 15, 2026
@github-actions

This comment has been minimized.

@github-actionsgithub-actionsBot mentioned this pull request May 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🤖 LabelOps — Conflict Resolution.

Conflicts detected in the following files:

  • .github/aw/actions-lock.json
  • .github/workflows/labelops-pr-maintenance.lock.yml

All conflicting files are under .github/, which is a protected path that LabelOps cannot modify. A maintainer will need to resolve these conflicts manually.

Generated by LabelOps — PR Maintenance · ● 12.6M ·

…size-exceeded
# Conflicts:
#	.github/aw/actions-lock.json
#	.github/workflows/labelops-pr-maintenance.lock.yml
@T-Gro
T-Gro enabled auto-merge (squash) May 18, 2026 08:40
@T-Gro
T-Gro merged commit c77851b into mainMay 18, 2026
4 checks passed
@github-project-automationgithub-project-automationBot moved this from New to In Progress in F# Compiler and ToolingMay 18, 2026
@github-project-automationgithub-project-automationBot moved this from In Progress to Done in F# Compiler and ToolingMay 18, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI-Auto-Resolve-ConflictsOpt-in: LabelOps merges main into this PR and resolves conflicts every 3hAI-Tooling-Check-BypassedTooling check: non-fork PR, not diff-analyzed

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

[aw] LabelOps — PR Maintenance failed

3 participants

@abonie@T-Gro