Skip to main content

Find out why a release lists no pull requests

Each release lists the pull requests it shipped under PRs, worked out from the pushes between it and the release before it. When PRs shows only a dash, the Range next to it says why, and tells you whether to wait, look at an earlier release or check what the release built. What a release records is in How Production QA works.

Before you start: the release run pages are part of Production QA, a plan feature. While your plan does not include it, opening the page of a release shows Not on your plan.

Who can do this: anyone who can view the project.

  1. Open the release's page. Release runs lists every way in, from the project's pipeline on the Tasks page or from an incident.
  2. On Overview, read PRs. A dash means Jaah found no pull request in what this release shipped.
  3. Read Range and the note after it:
    • A single short commit and no note: Jaah works out a range only for a production release started by a push. A release to a test environment, or one started by hand, lists no pull requests.
    • Pending: Jaah has not yet received the push that carried the released commit. Wait a few minutes; the page refreshes every 15 seconds.
    • Rollback, with the note head already shipped in deploy # and a number: this release shipped a commit an earlier release had already shipped. Its pull requests are listed on that earlier release.
    • A commit range with the note redeploy of the same commit: the release shipped the same commit as the one before it, so nothing new went out.
    • First recorded release: there is no earlier release of the project to this environment, so the range holds only the commits of the last push.
    • Partial: Jaah could read only part of the range, and pull requests in the rest are missing. The note says why, such as force push at a commit, a push between the two deploys was not recorded or head push not recorded.
  4. Read Other commits, when it shows. These are commits the release shipped that no pull request known to Jaah carries, such as commits pushed straight to the branch.
  5. If the release finished 10 minutes ago or more and Jaah still has no push for it, Pending turns Partial with head push not recorded: Jaah never received that push. Check the project's releases are connected, as in Turn on Production QA for a project.
  6. For a Rollback, open the earlier release it names to read its PRs. You can find it among the project's runs, as in Find a release run by environment or status.
  7. To see what the release built whatever its range, select the workflow and number under Run. It opens the run in your repository host.

A release with no pull requests can still have metrics and probes, so you can still check whether it broke production.