Rename /oz-review command to /warp-agent-review - #46
Merged
Conversation
Advertise /warp-agent-review as the PR-review comment command across the README and generated workflow templates. /oz-review keeps working as an unadvertised backwards-compatible alias so existing muscle memory and bookmarked comments don't break. The change is authored in examples/review-pr.yml (the source of truth) and propagated to .github/workflows/review-pr.yml and consumer-workflows/review-pr.yml via npm run gen-workflows.
Contributor
Author
|
This PR was generated with Warp. Comment    |
added 2 commits
August 21, 2026 15:23
The example workflow already carries this note; the live reusable workflow is the one a maintainer is most likely to prune the alias from, so it needs the reason too.
This reverts commit d67a6e3.
moirahuang
marked this pull request as ready for review
August 21, 2026 15:29
moirahuang
approved these changes
Aug 21, 2026
acarl005
approved these changes
Aug 21, 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
Renames the advertised PR-review comment command from
/oz-reviewto/warp-agent-review, per the org-wide rename. This repo hosts the only trigger surface that is literally a GitHub Actions workflow (issue_commentbody match), separate from thewarpdotdev/oz-for-osswebhook router, which is being renamed under separate cover./oz-reviewkeeps working as an unadvertised backwards-compatible alias — no hard cutoff — per explicit instruction from the requester.Changes
examples/review-pr.yml(source of truth): widened theissue_commenttrigger condition from an exact-equality check against/oz-reviewto accept either/warp-agent-reviewor/oz-review. Added a short comment explaining why the old command is retained. Updated the usage/prose comments to advertise/warp-agent-review..github/workflows/review-pr.ymlandconsumer-workflows/review-pr.yml: regenerated from the example vianpm run gen-workflows(these are generated files; do not hand-edit).README.md: updated the two prose references to the trigger command.Judgment call — flagging for reviewer
The trigger condition matches
github.event.comment.bodywith exact string equality. I widened it tobody == '/warp-agent-review' || body == '/oz-review'(the minimal change to satisfy "accept both spellings"). I deliberately did not additionally relax it to tolerate surrounding whitespace or trailing text (e.g./warp-agent-review please), even though theoz-for-ossrouter reportedly does something like that — that felt like scope creep beyond a rename, and changing matching semantics for existing exact-match consumers deserves its own look. Happy to widen further if that's preferred.Verification
examples/review-pr.yml,.github/workflows/review-pr.yml, andconsumer-workflows/review-pr.ymlparse as valid YAML (verified with theyamlpackage) and the generatedif:expression round-trips correctly with both command strings.npm run lint(ESLint) — clean.npx prettier --checkon the changed files — clean.npm test(vitest) — 27/27 passing (unaffected by this change; no code paths touched).act-based e2e workflow test (AGENTS.md) andactionlint— neitherdockernoractionlintwas available in this environment. The YAML parse + generator round-trip is the closest available substitute for confirming theif:expression is well-formed.