---
title: "Repair an unmapped GitHub deployment task | Proofline Help"
description: "If different programs deploy into one GitHub Environment, a repository-level service list can be too broad. The Inbox names the deployment task whose checks lack a service mapping."
url: https://proofline.sh/help/inbox-deploy-map-task/
---

[Help center](/help/)

# Repair an unmapped GitHub deployment task

If different programs deploy into one GitHub Environment, a repository-level service list can be too broad. The Inbox names the deployment task whose checks lack a service mapping.

## Map the named task to the services it deploys

Choose **Map deployment tasks** to open the repository’s **Advanced evidence**. Under **Deployment tasks**, enter the exact GitHub deployment task and select the ECS or Cloud Run services it changes. Map each applicable task once. A publication that changes no service can have an empty service selection.

Inspect a subsequent deploy of that same task. A successful check for a different deployment task, or a deployment that names no task, cannot clear this task’s gap.

## Related guides

-   [Clear Inbox setup tasks](/help/inbox-setup-tasks/)
