Repository navigation
docs(pagerduty): add the PagerDuty integration guide sections - #1248
Merged
Merged
Conversation
PagerDuty's Integration Directory review asks for an integration guide that follows its template and has a support section. Add curation chunks that give the PagerDuty toolkit page those sections: benefits, how it works, requirements, support, an integration walkthrough (install in PagerDuty, set up in Arcade), and how to uninstall. - Replace the two top callouts, which told every reader to register their own Scoped OAuth app, with one that sends Arcade Cloud users to the walkthrough and keeps the own-app guidance for self-hosted deployments and agents built for people outside the project. - Drop the auth chunk, which repeated the auth provider page and pointed at scopes "shown above". - Write the support address with a <wbr> before the @ so Cloudflare's email obfuscation doesn't turn it into a link that 404s for crawlers. - Re-sync pagerduty.json (documentationChunks and curationSourceHash only) so the preview deploy shows the page.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
EricGustin
marked this pull request as ready for review
October 16, 2026 22:28
… curation corpus The PagerDuty guide adds six chunks and removes two, so the checked-in corpus now holds 93 chunks.
… halve it The guide sat between the overview and the tools table, so readers scrolled past about 1,050 words before reaching the tools. Render it in the after_available_tools slot instead, and cut it to about 540 words while keeping every section from PagerDuty's template.
samkujovich
approved these changes
Oct 18, 2026
samkujovich
left a comment
samkujovich
left a comment
Contributor
There was a problem hiding this comment.
lgtm - seems like what they were looking for
This branch was successfully deployed
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.
Closes TOO-2603
Adds the sections from PagerDuty's integration guide template to the PagerDuty toolkit page, so PagerDuty can review the integration for its Integration Directory and publish Arcade's OAuth app.
pagerduty.json(documentationChunksandcurationSourceHashonly), so this preview shows the page, and raises the curation corpus test's chunk count to match.Verified:
validate-curationpasses for all 82 toolkits, the 529 toolkit-docs-generator tests pass, and the page renders locally with the guide after the tools table and before each tool's details.Before merging: confirm the install link (
https://<subdomain>.pagerduty.com/oauth-apps/PHRMXL1) in the arcadeai PagerDuty account.Note
Low Risk
Documentation and generated toolkit JSON curation only; no product or auth runtime changes.
Overview
Expands the PagerDuty toolkit docs with integration-guide sections (benefits, how it works, requirements, support, walkthrough, uninstall) as curated MDX chunks placed
after_available_tools, synced intopagerduty.json.The description callout is consolidated into a single info callout: Arcade Cloud users are directed to install Arcade’s OAuth app via the walkthrough, while self-hosted or multi-tenant setups still point to registering a Scoped OAuth app. The separate warning callout and the auth chunk (Bearer/OAuth boilerplate) are removed.
The curation corpus test expectation for total chunk count is updated 89 → 93.
Reviewed by Cursor Bugbot for commit f5cc85a. Bugbot is set up for automated code reviews on this repo. Configure here.