Grove shows a pull request on a project when the pull request is linked to it. If you can't see one, check these causes in order.
1. GitHub isn't connected
Grove sees pull requests only through the Grove GitHub app. If a project's Delivery tab shows Connect GitHub, a workspace admin must connect it first. See Connect GitHub.
2. The repository isn't one Grove reads
Grove only sees pull requests in the repositories an admin picked. Ask an admin to check Settings › GitHub. See GitHub connection errors.
3. The pull request isn't linked
A pull request links to a project in one of these ways:
The project ID is in the branch name or the PR title, such as
p-003-move-a-visit.The description has a link word right before the project ID, such as
Part of P-003.The description has a claims block with a
project:line.
These do not link:
Other words before the ID, such as
Fixes P-003orCloses P-003.A project ID on its own in the description.
A project ID between backticks, as code.
Fix it: paste Part of P-003, with the right project ID, into the pull request's description. Grove checks again the next time the pull request changes.
It shows on the project, but not on an outcome
Look at the bottom of the project's delivery section.
Pull requests that couldn't be matched
A merged pull request here was checked against every outcome, and Grove matched none.
An open pull request here names an outcome the project doesn't have.
If the pull request should count for an outcome, check its claims block. Quote the outcome's bold short name exactly as it is in the plan. See Claim outcomes in a pull request.
Grove is still checking these
The pull request merged, and Grove hasn't finished reading it. Wait. It moves to an outcome, or to the list above, on its own.