Skip to content

chore(ci): remove the one-off TML-3157 docs state migration - #200

Merged
wmadden merged 1 commit into
mainfrom
chore/remove-tml3157-migration
Aug 3, 2026
Merged

chore(ci): remove the one-off TML-3157 docs state migration#200
wmadden merged 1 commit into
mainfrom
chore/remove-tml3157-migration

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

Removes the migration script and workflow step added in #199, now that they have done their job.

The Deploy docs run migrated the composer-docs stack's 7 state rows from the legacy dev_runner scope to the default Branch's id and the subsequent deploy + smoke-check passed — the docs site serves from the migrated state at its unchanged URL. The step is idempotent, so nothing depends on removal timing.

Scope: deletes scripts/migrate-docs-state-tml3157.ts and its single step in deploy-docs.yml. Nothing else.

Verification: the diff is a pure revert of #199; merging triggers a docs deploy that should be a no-op (Done: 0 succeeded), which doubles as the post-migration acceptance check from TML-3157.

🤖 Generated with Claude Code

The migration ran green on 2026-08-03 (run 30850338761): 7 resource rows
re-staged from 'dev_runner' to the default Branch's id, deploy and
smoke-check passed. The step and script were one-off by design.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@wmadden-electric, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 35 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2a5b8da7-71e5-486c-983a-6c3ff5bbbf1e

📥 Commits

Reviewing files that changed from the base of the PR and between b0ade0e and ebc3360.

📒 Files selected for processing (2)
  • .github/workflows/deploy-docs.yml
  • scripts/migrate-docs-state-tml3157.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@wmadden
wmadden merged commit 3449f3e into main Aug 3, 2026
12 checks passed
@wmadden
wmadden deleted the chore/remove-tml3157-migration branch August 3, 2026 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants