ci: use DOCS_AGENT_GRAFANA_TOKEN for on-call reviewer assignment#205
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Hardcode the client on-call Grafana schedule ID (S1BRQ4BYUP5WN) in the oz agent prompt so reviewer assignment works without any additional variables. Uses --oncall-max-reviewers 2 to resolve both primary and secondary from the same schedule. Co-Authored-By: Oz <oz-agent@warp.dev>
dannyneira
force-pushed
the
danny/release-docs-oncall-schedule-id
branch
from
2f4f73d to
f18c411
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Overview
This PR updates the release docs automation to use DOCS_AGENT_GRAFANA_TOKEN instead of GRAFANA_API_KEY for Grafana on-call reviewer resolution, including the resolver script, environment preflight report key, skill guidance, and workflow prompt guidance.
Concerns
- No blocking correctness, security, or spec-drift concerns were found in the attached diff.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
hongyi-chen
approved these changes
Jun 11, 2026
This was referenced Jun 12, 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.
Summary
Updates the release docs workflow and scripts to use
DOCS_AGENT_GRAFANA_TOKEN(configured on the Docs Agent in prod Oz) instead ofGRAFANA_API_KEYfor resolving on-call reviewers. Also fixes the--pr-auto-merge/--pr-draftmutual exclusion bug on manual dispatch, updates the environment report key name for accurate release debugging, and removes staleGRAFANA_API_KEYreferences from all operational guidance.Changes
release-docs-update.yml: rule 7 now referencesDOCS_AGENT_GRAFANA_TOKEN;--pr-auto-mergeis only included whencreate_draft_pris false (fixes incompatibility with--pr-drafton manual dispatch); agent profile comment updatedresolve_oncall_reviewers.py: readsDOCS_AGENT_GRAFANA_TOKENinstead ofGRAFANA_API_KEYsetup_environment.py: checksDOCS_AGENT_GRAFANA_TOKEN; renames check key fromgrafana_api_key_present→docs_agent_grafana_token_presentso environment reports are accurate during debuggingSKILL.md: requirements and notes updated to referenceDOCS_AGENT_GRAFANA_TOKENSetup already completed ✅
DOCS_AGENT_GRAFANA_TOKEN.WARP_AGENT_PROFILE: set to as a GitHub Actions repository variable inwarpdotdev/docsDOCS_REPOSITORY_DISPATCH_TOKEN: added towarpdotdev/channel-versionssecrets (unblocks channel-versions PR #971)WARP_API_KEY: already present inwarpdotdev/docssecretsRemaining to merge
Once both are merged, the next Thursday stable release will automatically trigger a changelog PR with client on-call reviewers assigned and squash auto-merge enabled.
Co-Authored-By: Oz oz-agent@warp.dev