Add bulk upstream Mike synchronizer - #38
Merged
Merged
Conversation
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
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 changed
Open-Legal-Products/mikePRs;github-actions[bot]PRs onagent/upstream-sync-*branches into the existing exact-head dispatcher and merger.Safety boundaries
Automatic patches are limited to documentation, repository hygiene, frontend presentation markup, and tests. The clean runner rejects
.github, backend runtime, scripts, manifests, dependencies, lockfiles, auth/security/provider, schema/migration/Supabase, deployment/infrastructure, legal/privacy/governance/release/billing, environment, deletion, binary, rename, and oversized changes.The existing Baseline, failed-run reporting, exact-head checks, reviews, unresolved-thread checks, and mergeability gate remain authoritative.
Batch behaviour
Current limitation
Bot-authored synchronization PRs automatically verify and merge when green. A failed synchronization PR is reported but is not yet eligible for bounded Codex repair; that bot-specific repair exception will be added only after this intake and provenance path is validated end to end.