Use rebase merges and allow safe history rewriting - #3
Merged
Conversation
jdvmi00
force-pushed
the
chore/rebase-workflow
branch
from
September 6, 2026 01:38
9acf7bc to
c1ee9b8
Compare
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
1 participant
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.
Require rebase merging for all PRs and allow history rewriting with explicit force-with-lease guards. Update AGENTS.md, README, and the release workflow to match the owner’s requested policy.
GitHub now permits only rebase merges, requires linear history, and allows force pushes on main/develop while retaining required checks and PR rules. Main stays locked except during an authorized release or history repair.
Validation: repository checks and all 4 checker regression tests passed locally. Required Linux and Windows checks must pass before rebase merging.