# See your deploys next to your monitors > When something goes down right after a release, see that straight away, without comparing times in GitHub. Source: https://infranest.io/docs/see-your-deploys-next-to-your-monitors Last updated: 2026-10-26 --- See your deploys right next to your monitors and servers, so you can instantly spot whether a release caused an incident — no more comparing timestamps in GitHub. This is for anyone using GitHub to deploy who wants more context when something goes wrong. ## Overview - Link a GitHub repository to the monitors, servers or tags it affects. - Every deploy of that repository then shows up on the related incident (if it happened in the hour before) and as a marker on response-time and server charts. - A deploy only adds information — it never changes a monitor's status, uptime or incidents. ## Before you start - Connect GitHub using the InfraNest Automations app. A token connection does not receive deploys. - Decide what counts as a deploy for your repository. You'll choose one of these when you link it: - **A GitHub deployment** — your deploy job uses a GitHub environment (for example, `environment: production`), so GitHub records each deploy on its own. - **A workflow finishing** — you deploy with a GitHub Actions workflow that doesn't use an environment. Pick that workflow, and each finish counts as a deploy. - **A published release** — publishing a release on GitHub is how you ship. Not sure? Pick **A GitHub deployment**. If none are found, the form will tell you and offer **A workflow finishing** instead. ## Link a repository 1. Go to **Integrations** and open **GitHub**. 2. Go to **Connections & settings**, find **Deploys on your monitors** and click **Link a repository**. Once something is linked, click **Manage** there to see your links and add more. 3. Under **Repository**, pick the repository. Repositories are grouped by owner, and the ones that have already deployed are listed first. 4. Under **What counts as a deploy**, pick one of the three choices above. - For **A GitHub deployment**, choose under **Which deploys** whether all deploys count, or **Only deploys to one environment**, such as `production`, so test deploys don't show up. - For **A workflow finishing**, pick the **Workflow**, and if you like, a branch such as `main`. A failed run shows as a failed deploy. 5. Under **Shown on**, pick **Choose a monitor, server or tag**. 6. Click **Link**. If we can't find any deploys for the repository on GitHub, the form tells you before you link it. See the Before you start section above for what your deploy needs. ![See your deploys next to your monitors](/media/f4303f26-ac35-4a65-936c-2dfd38c4e964) When you link a repository, InfraNest also fetches its earlier deploys from GitHub, so your charts don't start empty. This takes a few seconds. Each link then shows one of these: - **last deploy {ago}** — it works. - **looking for earlier deploys…** — still fetching. Refresh the page in a moment. - **no deploys found on GitHub** — GitHub has never had a deploy for this repository. See the Before you start section above. - **no deploys received yet** — everything is set up, there just hasn't been a deploy yet. ### Link a repository from a monitor You can also link a repository from the monitor itself: 1. Open the monitor and go to its **Settings** tab. 2. In the **GitHub deploys** card, click **Link a repository**. 3. Pick the **Repository** and **What counts as a deploy**, then click **Link**. There is no **Shown on** choice here: the deploys show on this monitor. The card lists the repositories linked to this monitor, each with its last deploy time and a remove button. It only shows once GitHub is connected with the InfraNest Automations app. Repositories linked through one of the monitor's tags aren't listed there — manage those on the GitHub page, which **Manage in GitHub** opens. > [!NOTE] > Linking a tag covers everything with that tag, including monitors and servers you tag later. You can link the same repository more than once — for example, to a monitor and to a server. To stop showing a repository's deploys somewhere, remove its link from the same list, or from the monitor's **GitHub deploys** card. ## See deploys on an incident or chart 1. **On an incident:** open the incident on the **Incidents** page or on the monitor's page. Deploys from the hour before it started are listed at the top of its timeline, with a link to the deploy on GitHub and the pull requests it put live, so you can see what changed right away. A failed deploy is shown too, and labelled as failed. 2. **On charts:** each deploy appears as a dashed vertical line with a small flag. Hover over it to see the commit, the environment, who deployed it, and what it included — for example, *Includes #12, #14 · 3 commits*. Click it to open the deploy on GitHub. 3. The deploys in the chart's range are also listed under the chart, along with the repositories they come from and a **Manage** link back to your links. If nothing is linked yet, the chart offers **Link a repository** instead. > [!TIP] > With PagerDuty connected, a linked deploy also appears under **Recent changes** on the PagerDuty incident. ## Good to know - Deploys appear as soon as GitHub reports them. Earlier deploys are fetched when you link the repository, as far back as your plan keeps monitoring history. - Deploys are kept as long as your plan keeps monitoring history. - Only finished deploys are shown: successful, failed or errored. Deploys still in progress are not. - What a deploy included is worked out by comparing it with the previous successful deploy to the same place. The first deploy we know of has nothing to compare with yet, and says so. ## Troubleshooting - **The link says "no deploys found on GitHub".** Your deploy doesn't tell GitHub it happened. Either give your deploy job an environment (for example, `environment: production`), or remove the link and link the repository again with **A workflow finishing** and your deploy workflow. - **No deploys appear, and the link says "no deploys received yet".** Check that GitHub is connected with the InfraNest Automations app rather than a token. - **Deploys appear for the wrong environment.** Remove the link and link the repository again, choosing **Only deploys to one environment** and the environment you want.