GitHub Integration | Custory Changelog

We've expanded GitHub into a deeper workflow connection inside Custory — not just a place to send a task once and forget about it. Teams can now connect repository context, create linked GitHub issues, monitor pull requests, and use GitHub activity as part of automations. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **Product Management**.

## What's New

**Linked GitHub issues.** Create GitHub issues from Custory work and keep them attached to the relevant journey step or item, so engineering follow-up stays connected to the customer context that created it.

**Repository-aware setup.** Custory works with your connected repositories so issue creation and GitHub-based workflows feel grounded in your actual codebase rather than abstract references.

**Pull request visibility.** GitHub pull request activity is now part of the workflow surface, making it easier to connect delivery progress back to journey work.

**GitHub-driven automations.** Use GitHub pull request events — PRs being opened or merged — as automation triggers. Code activity can now drive follow-up work in Custory instead of product teams needing to notice progress manually.

## Why it matters

Customer journey work often breaks down at the handoff into engineering. By connecting GitHub more deeply into Custory, that handoff becomes easier to trace, easier to automate, and easier to keep tied to the original customer problem — so product and engineering stay aligned around what changed and why.

We've expanded GitHub into a deeper workflow connection inside Custory — not just a place to send a task once and forget about it. Teams can now connect repository context, create linked GitHub issues, monitor pull requests, and use GitHub activity as part of automations. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **Product Management**.

## What's New

**Linked GitHub issues.** Create GitHub issues from Custory work and keep them attached to the relevant journey step or item, so engineering follow-up stays connected to the customer context that created it.

**Repository-aware setup.** Custory works with your connected repositories so issue creation and GitHub-based workflows feel grounded in your actual codebase rather than abstract references.

**Pull request visibility.** GitHub pull request activity is now part of the workflow surface, making it easier to connect delivery progress back to journey work.

**GitHub-driven automations.** Use GitHub pull request events — PRs being opened or merged — as automation triggers. Code activity can now drive follow-up work in Custory instead of product teams needing to notice progress manually.

## Why it matters

Customer journey work often breaks down at the handoff into engineering. By connecting GitHub more deeply into Custory, that handoff becomes easier to trace, easier to automate, and easier to keep tied to the original customer problem — so product and engineering stay aligned around what changed and why.