---
title: "How to Link GitHub Pull Requests to Customer Feedback"
summary: "Connect GitHub pull requests to the feature requests behind them: manual and automatic linking, PR status on the post, and rules that move a request when its PR merges."
date: 2026-11-13
author: "FeatureOS"
canonical: https://featureos.com/blog/link-github-pull-requests-to-customer-feedback
markdown: https://featureos.com/blog/link-github-pull-requests-to-customer-feedback.md
lastUpdated: 2026-11-13
categories: ["guides"]
readingTime: 2
---

To link a GitHub pull request to customer feedback, attach the PR to the feature request it implements, so the request shows the PR's state and the request's status changes as the PR moves. In FeatureOS you can link manually from the post, or automatically by pasting the post's URL into the PR description. Status rules then move the post when the PR is opened, marked ready, merged or closed.

## Why link pull requests to feedback?

A merged PR says "this shipped". It does not say who asked for it. Without a link, someone has to remember which customers voted for the request, find the post, change its status and tell them. That step is the one that gets skipped, and customers never hear back. Linking the PR to the post makes the status update a side effect of merging. See [how to close the feedback loop](/blog/how-to-close-the-feedback-loop).

## Two ways to link a PR to a post

**Manual.** Open the post in FeatureOS, click **Link Issue**, and choose the pull request. Works for PRs that already exist.

**Automatic.** Put the post's URL in the PR description. FeatureOS finds it and links the PR. Add it to your PR template so developers do it once, not per PR.

Linked PRs show on the post with chips for state (open, draft, merged, closed), label and author.

## Move the post when the PR moves

Status rules support these pull request events:

| PR event | Example status for the post |
|---|---|
| Opened | In progress |
| Draft | Planned |
| Ready for review | In review |
| Merged | Shipped |
| Closed without merging | Planned (back to the queue) |

Pick the statuses that match your own workflow. Voters on the post are notified through your normal status flow when it changes.

## Set it up

1. In FeatureOS, open **Organization Settings > Integrations > GitHub** and connect your repositories ([integration page](/integrations/github)).
2. Accept the updated GitHub permission. Pull request features need it; issue linking works without it.
3. Add status rules for the PR events you care about.
4. Add the post URL line to your PR template.

Availability note: this needs an updated GitHub permission (pull requests, read-only). An admin accepts it once in GitHub; existing issue linking is unaffected.

## What about Linear or Jira?

If engineering tracks work in Linear, PRs link to Linear issues through branch names and magic words. That covers the engineering side. Linking the PR to the FeatureOS post covers the customer side, so the two do not conflict. Compare [Linear's integration](/integrations/linear) and [Jira's](/integrations/jira).

Next: [auto-draft a changelog from merged pull requests](/blog/auto-draft-changelog-from-pull-requests).