Repository navigation
Allow explicitly configured scoped acceptance request budgets - #34
Merged
Merged
Conversation
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
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.
The operator explicitly requested raising the disposable acceptance budget immediately after the initial 16 requests were exhausted. A quota-only policy PR still needs a genuine AI review under the required App check, so protected policy cannot bootstrap itself when its existing budget is exhausted.
Add disabled-by-default
ACCEPTANCE_USER_PER_DAYoperator configuration, bounded to 1–1000 and applied only when BOTH existing acceptance installation/repository IDs match independently verified request identity. It changes only the per-user admission limit for that exact disposable tenant. Keep every counter, duplicate/cooldown/rerun/repository/installation/concurrency limit, authorization, credential boundary and protected-branch/AI approval requirement. Public callers cannot supply this configuration. Rejection reports use the effective limit; persisted protected review/merge policy remains unchanged for independent publication checks. Clear the temporary configuration once the normal quota-only policy PR is merged.No D1 migration, credential, Environment, reusable-workflow or runner change. Keep the current strict trusted pin during caller cutover; never accept alternative pins together.
Validation: full Node 24 check (198 tests), including exact repository+installation isolation, default policy retention, no counter reset and invalid configuration rejection. Full CI required before normal merge/deployment.