chore: update repository references after transfer#4
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (13)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
@coderabbitai full review |
Rate Limit Exceeded
|
|
@coderabbitai approve |
✅ Action performedComments resolved and changes approved. |
|
/trunk merge |
|
😎 Merged successfully - details. |
Updates post-transfer repository references and moves workflow runtime secret access
to the shared 1Password
Github Secretsvault.This only changes repositories that were part of the
slipstream-engmigrationinventory.
Secret-loading changes:
OP_SERVICE_ACCOUNT_TOKENas the only GitHub Actions bootstrap secret1password/load-secrets-action@v4op://Github Secrets/...references for cargo/Hex publish tokens,the GitHub release automation PAT, and the release signing SSH key
NPM_TOKENGITHUB_TOKENusage unchangedRunner migration:
self-hosted-gregorwithubuntu-latestwhere the transferredpersonal-account repos no longer have an eligible shared runner
nix developsteps where neededVerification run where applicable:
git diff --checkyaml.safe_loadactionlintNotes:
migrated source repositories.
release automation PAT, and release signing key.
GH_RELEASE_AUTOMATION_TOKENis a fine-grained PAT. Required repositorypermissions: Contents read/write, Pull requests read/write, Issues read/write
for release-please repos, Metadata read-only. Do not grant Actions/Workflows
unless release automation must edit workflow files; do not grant
Administration unless protected tag rules block release tag creation.
GitHub repository and publish workflow before tokenless npm publishing works.