chore: freeze docs automation during migration - #349
Merged
Conversation
Suspend the two unattended writers to `main` for the duration of the documentation migration, so the tree stops moving while it is restructured. Removes the weekly `schedule` trigger and the `gh pr merge --admin` step, which merged the sync PR without human review and bypassed the base-branch status-check policy. `workflow_dispatch` remains as the manual path: it opens a pull request for a human to merge. The job's `if:` guard is left as-is so restoring the schedule is a pure re-add of the `schedule` block.
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.
First step of the documentation migration: stop automation from writing to
mainunattended while the tree is being restructured.sync-openapi.ymlran weekly on cron and then self-merged withgh pr merge --squash --admin, bypassing the base-branch status-check policy. That conflicts with the anchor pass, the Geneva removal, and the page moves, all of which need a tree that does not move underneath them.This removes the
scheduletrigger and the auto-merge step.workflow_dispatchstays as the manual path — it opens a pull request for a human to merge. The job'sif:guard is untouched so restoring the schedule later is a pure re-add of thescheduleblock.Two companion actions are manual and happen outside this PR:
mainto thedeploy-freezebranch (pinned at 03ad18f), so the site keeps serving while deploys pause.mintlify[bot]catch-up writer is stopped.Human documentation pull requests continue to merge to
mainas normal — they queue and ship together at the migration's first cutover.