Skip to content

docs: drops the API reference's autosquash hide-list, the field is gone upstream - #13055

Merged
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/change-watch--drop-dead-autosquash-hide-from-api-reference
Sep 29, 2026
Merged

mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/change-watch--drop-dead-autosquash-hide-from-api-reference

Conversation

@mergify-ci-bot

Copy link
Copy Markdown
Contributor

The API reference carried a hide-list whose only entry was autosquash, stripping
that field from the OpenAPI document before rendering. autosquash has since left
both published schemas — it appears nowhere in public/api-schemas.json — so the
list 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: autosquash has zero occurrences in public/api-schemas.json, and the
configuration schema dropped its three autosquash definitions (two queue-rule
copies and the rebase action) 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.

@mergify
mergify Bot deployed to Mergify Merge Protections September 29, 2026 04:19 Active
@mergify

mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 5 merge protections satisfied — ready to merge.

Show 5 satisfied protections

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 1
    • author = dependabot[bot]
    • author = renovate[bot]
    • all of:
      • -head ~= ^docs-agent/
      • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@mergify
mergify Bot requested a review from a team September 29, 2026 04:21
@mergify

mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
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

@mergify mergify Bot added the queued label Sep 29, 2026
@mergify
mergify Bot merged commit 74300fa into Mergifyio:main Sep 29, 2026
12 checks passed
@mergify mergify Bot removed the queued label Sep 29, 2026
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

1 active deployment
Mergify Merge Protections — 47cb2e14 Deployed Sep 29, 2026 by mergify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants