Skip to content

chaos-pr-bundle-fuzzer: make PR count deterministic at 5 and expand merge-tree strategy coverage #32378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 2 commits into from
May 15, 2026
+4 −4
Merged

chaos-pr-bundle-fuzzer: make PR count deterministic at 5 and expand merge-tree strategy coverage #32378

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a471818
Initial plan
Copilot May 15, 2026
854837c
Require 5 PRs and complex merge strategies in chaos fuzzer
Copilot May 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/chaos-pr-bundle-fuzzer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Generate randomized "agent personas" that each perform a small change scenario,

## Hard Requirements

1. Create at most **5 PRs per run**.
1. Create exactly **5 PRs per run**.
2. Every PR branch name must start with `chaos/`.
3. Every PR body must include this exact sentence (plain text, no markdown formatting):
This pull request is an automated chaos test for safe-output create-pull-request bundling.
Expand All @@ -61,10 +61,10 @@ For each run:

1. Load previous ledger if present.
2. Build a randomized plan:
- Random PR count between 1 and 5.
- Always generate 5 PR scenarios.
- Random personas (examples: cautious maintainer, rushed intern, refactor zealot, docs tidy bot, flaky fixer).
- Random strategy mix (single commit, two commits, amend, staged subset, minor rename, line-ending variant).
3. Prefer strategies that were under-tested in previous runs (fuzzy balancing, not strict rotation).
- Random strategy mix (single commit, two commits, amend, staged subset, minor rename, line-ending variant, multi-parent merge commit, octopus merge, diverged history reconciliation).
3. Prefer strategies that were under-tested in previous runs while balancing simple and complex strategy categories across runs.
Comment on lines +64 to +67

## Per-PR Scenario Steps

Expand Down