Repository mappings

The Repository Mappings panel (/home/repository-mappings) lets you tell Delego which GitHub repository to use for a given Linear project. Without a mapping, Delego can only target a repository if the issue carries an explicit repo label — mappings let you skip that label entirely for a given project.

How mappings work

When a job is claimed by a runner, Delego checks whether the job already has a repository slug (resolved from a repo label on the issue). If not, it looks for a matching repository mapping and uses that instead. Mappings are matched by Linear project — the most specific match wins.

A mapping can apply to:

• A specific Linear project — only issues from that project use this mapping.
• All projects — a catch-all that applies to any issue without a more specific match.

Mapping cards

Each active mapping is shown as a card with:

• The Linear project name (or "All projects" for a catch-all mapping).
• An arrow to the GitHub repository slug in owner/repo format.
• Three policy chips showing the publishing behaviour for completed jobs:
  • Auto-push — whether the runner automatically pushes the branch to GitHub.
  • Auto-create PR — whether a pull request is opened automatically after the branch is pushed.
  • Draft PR — whether the pull request is opened as a draft.
• The last updated timestamp.
• Edit and Archive buttons.

Adding a mapping

Click Add mapping (top-right button, or the dashed + tile in the grid). A dialog opens with the following fields:

Scope — choose whether this mapping applies to all Linear projects or a specific one. If you choose a specific project, a dropdown lets you pick from the projects in your connected Linear workspace.

Repository — the GitHub repository in owner/repo format (e.g. myorg/frontend). This must exactly match the repository slug on GitHub.

Publishing policy — three toggles that control what happens when a job completes:

Toggling auto-push off disables the PR toggles. Toggling auto-create PR off disables the draft toggle.

Editing a mapping

Click Edit on any mapping card. The same dialog opens pre-filled with the existing values. All fields can be changed, including the scope and repository slug.

Archiving a mapping

Click Archive on a mapping card to soft-delete it. Archived mappings stop matching new jobs but are not permanently deleted — they are shown in a collapsed Archived section at the bottom of the panel and can be restored from there.

Archiving is the right action when you want to stop routing jobs through a particular mapping without losing the configuration.

Missing Linear installation

If you have not yet connected a Linear workspace, the panel shows a prompt to complete the Linear setup before adding mappings. Repository mappings are matched by Linear project, so the integration must be active for the project picker to work.