Skip to content

Remove obsolete Oz-agent GitHub Actions workflows#93

Merged
hongyi-chen merged 1 commit into
mainfrom
hyc/remove-oz-agent-workflows
May 18, 2026
Merged

Remove obsolete Oz-agent GitHub Actions workflows#93
hongyi-chen merged 1 commit into
mainfrom
hyc/remove-oz-agent-workflows

Conversation

@hongyi-chen
Copy link
Copy Markdown
Collaborator

Summary

Removes the two Oz-agent GitHub Actions workflows from this repo because they're failing on every PR and have been superseded by the Oz management webhook flow.

Why

  • warpdotdev/docs is a public repo and doesn't have access to the org-level WARP_API_KEY secret, so Auto PR Review fails on every PR with warp_api_key must be provided. (example failed run: https://github.com/warpdotdev/docs/actions/runs/26031884808/job/76519685475?pr=91).
  • The same issue affects Respond to Comment (@oz-agent mentions), which also reads secrets.WARP_API_KEY.
  • Per @captainsafia in Slack, the Oz management flow now provides PR review coverage via webhooks, and the GHA workflows are no longer necessary.

Changes

  • Delete .github/workflows/review-pr.yml.
  • Delete .github/workflows/respond-to-comment.yml.
  • .github/workflows/ci.yml is untouched (build, typecheck, link-check, audit).

Notes

  • src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx references files named review-pr.yml/respond-to-comment.yml, but those links point to examples in the warpdotdev/oz-agent-action repo, not these local workflows — no doc changes needed.

Conversation: https://staging.warp.dev/conversation/4f8595a1-4ce2-4328-90a7-a9da74e28b05
Run: https://oz.staging.warp.dev/runs/019e3bee-3685-72af-97d2-165820c71904
Plans:

This PR was generated with Oz.

These workflows depend on a `WARP_API_KEY` org-level secret that isn't
exposed to the public `warpdotdev/docs` repo, so they fail on every PR
(example: https://github.com/warpdotdev/docs/actions/runs/26031884808).

PR review coverage and `@oz-agent` comment responses are now handled by
the Oz management webhook flow, making these workflows redundant.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 18, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 18, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 18, 2026 4:39pm

Request Review

@hongyi-chen hongyi-chen marked this pull request as ready for review May 18, 2026 16:52
@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 18, 2026

@hongyi-chen

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR removes the obsolete Respond to Comment and Auto PR Review GitHub Actions workflows. The removed workflows depended on secrets.WARP_API_KEY; this public repository cannot access that org-level secret, and the PR does not change the existing CI workflow.

Concerns

  • No blocking correctness or security concerns found in the changed lines. The diff removes failing automation paths and their repository write permissions without introducing new execution paths, dependencies, or secret handling.

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 hongyi-chen merged commit 12d36f0 into main May 18, 2026
8 checks passed
@hongyi-chen hongyi-chen deleted the hyc/remove-oz-agent-workflows branch May 18, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants