docs: fix Warp app naming across the integration docs - #577
Conversation
The Oz -> Automation Platform rename (0e8c5a6) replaced references to 'the Oz app' installed in Jira with {VARS.WARP_AUTOMATION_PLATFORM}. That's the platform's name, not the Atlassian app's name -- the app the reader installs and finds in Manage apps is named Warp. Replace the ten Automation Platform references with Warp app naming.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment   |
Extends the Jira integration fix to the rest of the integration docs.
For each {VARS.WARP_AUTOMATION_PLATFORM} use, replace it with Warp / the
Warp app where the sentence names the installed third-party app or the
actor posting/acting inside that tool, and leave the variable where the
sentence describes the platform itself (triggers, environments, OIDC
federation).
- quickstart.mdx: fixed 9 of 10 uses (Slack app install/authorize steps
and the actor that acknowledges/posts in Slack); left the platform-level
"integrations" and "consistent instructions across every run" uses.
- linear.mdx: fixed all 4 uses (install, uninstall, and the actor that
clones repos and works the issue).
- reference/cli/integration-setup.mdx: fixed 2 of 3 uses (configuring
the app, installing it into Slack/Linear); left the link to the
platform overview page.
- cloud-providers.mdx, bitbucket.mdx, azure-devops.mdx, gitlab.mdx,
index.mdx: audited, no changes -- all uses describe the platform
(triggers, OIDC federation) rather than an installed app.
warp-agent-staging
Bot
changed the title
The --prompt is supplied to each run's agent, not the platform or "Warp" (which can also read as the desktop app). Say "give agents consistent, reusable instructions across every run" instead.
![warp-agent-staging[bot]](https://avatars.githubusercontent.com/in/2196476?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
Extends the Jira app-naming fix across the integration docs, swapping the Automation Platform variable for Warp only where the sentence's subject is the installed app rather than the platform. One open question about external product labels needs a human.
Concerns
- The install, removal, and selection instructions in
platform/integrations/linear.mdx(114, 127, 132),platform/integrations/quickstart.mdx(33, 45), andreference/cli/integration-setup.mdx(58, 229) rest on Slack and Linear displaying the installed integration as Warp, which no product console was available here to confirm. A stale label would send an admin looking for an app that is not in the list, which is the same defect this PR set out to fix. A Slack workspace admin and a Linear workspace admin should confirm the live listing labels, and "Warp app" should stay only where confirmed. Jira is settled:warp-server/forge-jira/manifest.yml:11declares the Rovo agent name asWarp.
Verdict
Checks: build pass, tests n/a, CI green, visual proof n/a
Found: 0 critical, 0 important, 0 suggestions, 0 nits, 1 question
Responding as wilson: Open session · View factory task
|
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 Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR updates integration documentation terminology so installed third-party app and acting-bot references use "Warp" or "the Warp app" instead of the Automation Platform variable. The changed lines are consistent with the PR scope, and I did not find security, correctness, style, comment, test, or spec-drift concerns in the attached diff.
Concerns
- None.
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
2 participants
Summary
Extends the Jira integration app-naming fix to the rest of the integration docs. The Oz → Automation Platform rename blanket-replaced "Oz"/"the Oz app" with
{VARS.WARP_AUTOMATION_PLATFORM}across the docs, but several integration pages also used it for the installed third-party app itself (the thing a Slack, Linear, or Jira admin finds, installs, authorizes, or removes) rather than the platform that runs and coordinates agents. That app is named Warp, not "the Automation Platform."Scoping decision from @jasonkeung (Slack DM, relayed via the docs owner): use the Automation Platform variable where it's actually the platform, but refer to the third-party apps as "Warp" / "the Warp app." Scoped to the integration docs for now.
Changes
For each
{VARS.WARP_AUTOMATION_PLATFORM}use in scope, judged whether the sentence names the installed app/acting bot (→ "Warp" or "the Warp app") or the platform itself (→ left as the variable).src/content/docs/platform/integrations/jira.mdx(10 uses, done in the original commit) - all fixed; see prior commit.src/content/docs/platform/integrations/quickstart.mdx(10 uses found, 9 fixed) - fixed the Slack app authorize/connect steps and the acting-subject sentences ("Warp acknowledges the request...", "Warp posts a link/summary...", "Warp reads the Slack thread..."), plus "give agents consistent, reusable instructions across every run" (the--promptis supplied to each run's agent, not the platform, and not "Warp," which could also be misread as the desktop app there). Left one platform use ("{VARS.WARP_AUTOMATION_PLATFORM} integrations let you trigger cloud agents...").src/content/docs/platform/integrations/linear.mdx(4 uses, all fixed) - "Warp clones the repositories..." (acting subject), "install the Warp app into your Linear workspace," "To remove the Warp app from Linear," and "Select Warp from the list of installed agents" (matching the Jira fix's bolded UI-list-entry style).src/content/docs/reference/cli/integration-setup.mdx(3 uses found, 2 fixed) - "Configure the Warp app with an integration" and "install the Warp app into your Slack workspace or Linear workspace." Left the link to the platform overview page ([{VARS.WARP_AUTOMATION_PLATFORM}](/platform/overview/)).No changes (audited, all uses are legitimately the platform):
src/content/docs/platform/integrations/cloud-providers.mdx(13 uses) - all describe OIDC token issuance and federation mechanics (the platform), not an installed app. AWS/GCP OIDC federation has no analogous "installed app in a marketplace" concept.src/content/docs/platform/integrations/index.mdx(1 use) - "Integrations run on the Automation Platform... which handles the trigger, the environment, and the record of each run" is platform infrastructure.src/content/docs/platform/integrations/bitbucket.mdx,azure-devops.mdx,gitlab.mdx(1 use each) - all read "your environment works with any {VARS.WARP_AUTOMATION_PLATFORM} trigger—Slack, Linear, schedules, or the CLI," which is about triggers (platform), not an installed app.src/content/docs/factories/integrations/**- confirmed zero uses; already clean.Verification
npm install && npm run build- succeeds with no errors..agents/skills/style_lint/style_lint.py --changed- 0 new issues from this PR. It reports 21 pre-existing issues (header case, unrecognized bolded terms, one screenshot width) across the 4 changed files; confirmed every flagged line is byte-identical toorigin/main(i.e., not touched by this change).dist/client/platform/integrations/quickstart.md,dist/client/platform/integrations/linear.md,dist/client/reference/cli/integration-setup.md) to confirm the substitutions read correctly to the reader, not just in the diff.quickstart.mdxactually has 10 uses (not 9), all others matched.Not verified / follow-up
src/content/docs/platform/integrations/slack.mdx(uses "the Warp app" for install/authorize/remove, plain "Warp" for the acting bot) and the fixedjira.mdx, both of which were presumably verified against the real product when they were written/fixed.@Ozreference insrc/content/docs/platform/integrations/linear.mdx:141("Linear not detecting @oz") that should say@warp— unrelated to the{VARS.WARP_AUTOMATION_PLATFORM}bug and out of this PR's scope, flagging as follow-up work.