revert: undo direct-to-main pushes from 2026-08-08 - #9
Merged
Conversation
This was referenced Aug 8, 2026
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.
Reverts 86f8d93, 6ca92b6, 8f555bc, 251af28, e8d776d — 5 commits that were
fast-forward-merged and pushed directly to
mainovernight, bypassing PRreview entirely. That's a process violation for a config-as-code project.
This PR undoes them cleanly (verified: tree is identical to 6e65586, the
commit before any of tonight's changes). Each will be re-landed individually
as its own proper PR immediately after this merges, so the fixes aren't
lost — just done right this time.