Skip to Content
ProjectsLink boards & repos

Link boards & repos

A project is just a container until you connect it to GitHub. Linked repos are where the project’s issues and milestones actually live; linked GitHub Projects boards are optional mirrors for the project’s status. You manage both from the detail page’s Settings menu.

Prerequisite: the project must belong to the same GitHub org as the repos and boards you link. dev-pulse only shows repos/boards in that org.

Until at least one repo is linked, the project page shows a red “No linked repos” banner and:

Linking a repo is almost always the first thing you do on a new project.

Linking a GitHub Projects board

From Settings › + Link a board… (in the Boards group), the Link-a-board dialog lists the org’s GitHub Projects v2 boards. Pick one to link. The link is what lets dev-pulse mirror the project’s status between its own model and the GitHub board.

Once linked:

  • the board shows as a blue badge in the project header (clickable through to GitHub),
  • it appears in the Boards section of the Settings menu with an Unlink action,
  • the Linked surfaces KPI count goes up.

To unlink, open Settings and click Unlink next to the board. Unlinking doesn’t delete anything on GitHub — it just stops dev-pulse tracking the board for this project.

Managing repos

From Settings › Repos › Manage repos…, the repo picker lets you choose which repos in the org this project draws from. Toggle repos on/off to control which ones contribute issues and milestones.

Once linked:

  • each repo shows as a green badge in the project header (clickable through to GitHub),
  • the repo’s issues become available to add to the workbench,
  • the repo’s milestones appear on the milestones strip,
  • the “No linked repos” banner disappears.

The mirror status

When dev-pulse syncs a linked board, each link shows a mirror status row:

  • on success: Last sync: 14:23:07 ✓
  • on failure: Last sync: failed — <message>

If a link is failing, use Re-link to unlink and re-open the link dialog and try again.

What writes through to GitHub

Some actions on a linked project write through to GitHub (via the dev-pulse GitHub App, or a personal access token if that’s how your install is configured). Specifically:

  • milestone create / edit / close / reopen / delete,
  • dates mirrored to a linked GitHub Projects board.

Everything else (saved views, the lead, status, tags, the project’s own name) lives only in dev-pulse.

Next

Last updated on
Schedule