Repository navigation
feat(bot): configure production Jev service and API root - #452
Merged
Merged
Conversation
AsperforMias
requested review from
KurosawaGeeker and
hikariming
as code owners
October 7, 2026 14:50
AsperforMias
temporarily deployed
to
Production
October 7, 2026 15:02 — with
GitHub Actions
Inactive
AsperforMias
requested a deployment
to
Production
October 7, 2026 15:02 — with
GitHub Actions
In progress
This branch is being deployed
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.
Jev previously used a fixed endpoint and the production Bot selected the unconfigured LLM provider. Add an operator-configurable
JEV_BASE_URLAPI root and select Jev in production, using the separately installedOPENROUTER_API_KEYWorker Secret. Local/staging keeps the LLM provider, and repository intent-label opt-ins retain their current values.The classifier appends
/alpha/decisions, requires HTTPS, rejects credentials/query/fragment/ambiguous URL syntax, and rejects redirects. Invalid configuration disables readiness and fails before any request. Update generated bindings, tests and operator documentation. No credentials are committed.Validation: 274 Bot tests, root typecheck and lint, production Worker dry build, and independent read-only security review passed. A real OpenRouter Jev request with synthetic issue text selected
bugat 0.91 using the configured endpoint. No GitHub label writes or repository setting changes were performed.