Skip to content

docs: contributor-owned local secret setup - #122

Merged
j-cadena-g merged 1 commit into
mainfrom
docs/dev-friendly-setup
Aug 11, 2026
Merged

docs: contributor-owned local secret setup#122
j-cadena-g merged 1 commit into
mainfrom
docs/dev-friendly-setup

Conversation

@j-cadena-g

Copy link
Copy Markdown
Owner

Summary

  • Clarify that contributors create and use their own 1Password Environments (no shared amigo (dev) vault to request access to)
  • Treat amigo (dev) / amigo (prod) as suggested display names; fence Workers Builds / deploy as operator-only
  • Align SECURITY, example manifests, and dev:verify hints with the same framing

Test plan

  • Skim README Quick Start + CONTRIBUTING first-run as a new contributor
  • Confirm operator deploy / Workers Builds sections still make sense for maintainers
  • No app/runtime behavior changes (docs + verify message strings only)

Clarify that each developer creates their own 1Password Environment; amigo (dev)/(prod) are display-name suggestions, not shared vaults to join.
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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

Run ID: 8947892c-1047-40f0-be8c-23aa1539a9be

📥 Commits

Reviewing files that changed from the base of the PR and between 9c225d1 and 567d26d.

📒 Files selected for processing (7)
  • CONTRIBUTING.md
  • README.md
  • SECURITY.md
  • apps/web/.deploy.env.example
  • apps/web/.op/refs.env.example
  • apps/web/.wrangler.secrets.example
  • scripts/verify-dev-environment.mjs

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

@j-cadena-g
j-cadena-g merged commit 6586b46 into main Aug 11, 2026
8 checks passed
@j-cadena-g
j-cadena-g deleted the docs/dev-friendly-setup branch August 11, 2026 21:04
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.

1 participant