ci(warden): Pass Warden Service URL and token to the review job - #210
Merged
Conversation
Expose the org-wide WARDEN_SERVICE_URL variable and WARDEN_SERVICE_TOKEN secret to the Warden job so the action can reach Warden Service. The URL comes from the `vars` context rather than `env`, since org and repository variables are only available through `vars` — reading it from `env` would self-reference the job's own env block and resolve to an empty string. Co-Authored-By: Claude <noreply@anthropic.com>
gricha
approved these changes
Aug 14, 2026
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
2 participants
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.
Expose the org-wide
WARDEN_SERVICE_URLvariable andWARDEN_SERVICE_TOKENsecret to the Warden job so the action can reach Warden Service.The URL is read from the
varscontext rather thanenv. Org and repository variables are only available throughvars; reading it fromenvwould self-reference the job's ownenvblock and silently resolve to an empty string.Two things worth a reviewer's eye:
WARDEN_OPENROUTER_API_KEY, which the "Check Warden credentials" step gates on with a!= ''check, a missing service URL or token will not fail the job. Left as-is deliberately so Warden reviews keep working if Warden Service is unconfigured or down, but happy to add a check if we would rather know loudly.Draft until the org-level access policy is confirmed to cover the repos using this workflow.