Search blocks by description or jump to a page.
GitHub integration page with connected account, permissions list, configure rows, and disconnect consequence.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Integration Detail Panel is the full GitHub integration page: a Connected badge next to the name, the connecting account shown as acme-org connected by Avery Stone on May 14, 2026, three what-it-does bullets (commits linked, deploy statuses posted, repository activity on the project timeline), and the complete permissions list rendered honestly with scope codes (repo:read, statuses:write) and the explicit note that it cannot read code contents, push, or act outside acme-org. Configure rows cover the repository allowlist and environment mapping. The disconnect row states its consequence before you click: deploy statuses stop posting immediately and linked pull requests lose their project references, reconnecting does not restore them.
Permissions and configure rows are separate arrays. The consequence line on disconnect is the copy that prevents a support ticket at 2 am.
Reach for this block as the detail page for a single integration, wired to your integration config endpoint and the connected account from your OAuth record. The disconnect action should call your revoke endpoint and redirect back to the gallery.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the OAuth integration detail page. Other detail panels:
Tip: the permissions list earns trust only if it is the complete list; the block says so explicitly and that line should stay.