docs: drops the API reference's autosquash hide-list, the field is gone upstream - #13055
Merged
Conversation
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
JulianMaurin
approved these changes
Sep 29, 2026
Contributor
Merge Queue Status
This pull request spent 2 hours 37 minutes 42 seconds in the queue, including 3 minutes 13 seconds running CI. Required conditions to merge
|
49 tasks
mergify Bot
pushed a commit
that referenced
this pull request
Sep 29, 2026
…field is gone upstream (#13061) `src/util/sanitizedConfigSchema.ts` deep-cloned the synced configuration schema and deleted every `autosquash` key from it before the reference tables rendered. `autosquash` has left the schema: the engine stopped accepting it on 2026-09-24, and `public/mergify-configuration-schema.json` has held zero occurrences since the 2026-09-25 sync. The list matched nothing, and the module cloned and walked the whole schema on every build to delete a key that was not there. The eight importers now read the JSON directly. None of them mutates it, so the clone bought nothing either. Rendered pages are unchanged. The same file is served verbatim at `/mergify-configuration-schema.json`, so the list never hid the field from anyone reading the schema, only from the tables. This is the configuration-schema half of what #13055 did for the API reference. Restoring a hide-list for a future field is a revert. The removal's changelog entry (2026-09-29, "`autosquash` has been removed") is published separately through the changelog pipeline. Fixes MRGFY-9851 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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.
The API reference carried a hide-list whose only entry was
autosquash, strippingthat field from the OpenAPI document before rendering.
autosquashhas since leftboth published schemas — it appears nowhere in
public/api-schemas.json— so thelist matched nothing and the walk it drove recursed over the whole document on
every build to delete a key that was not there. Removing it changes no rendered
page.
Evidence:
autosquashhas zero occurrences inpublic/api-schemas.json, and theconfiguration schema dropped its three
autosquashdefinitions (two queue-rulecopies and the
rebaseaction) in this window.Open question: whether to keep the hiding mechanism for the next field that needs
it. I removed the whole block rather than leaving an empty list with the walk
still wired up, on the grounds that git history is where a dormant mechanism
belongs; restoring it is a revert if a field needs hiding again.