Skip to content
Halyard Docs Halyard Docs Halyard Docs

GitHub

Connecting GitHub turns your team’s pull-request activity into work events Halyard can report on. This is a source for Workspace admins (Reader A) who want delivery metrics in the knowledge layer.

What you get: work events, not searchable knowledge. GitHub produces episodic records of delivery — PRs opened, merged, and closed, plus reviews — that you list and filter by type, author, repo, and time. It does not make PR descriptions or diffs semantically searchable; if you want to search a decision, capture it as knowledge instead.

What it produces

Section titled “What it produces”

GitHub events arrive as work-event types including:

  • pull_request_opened
  • pull_request_merged
  • pull_request_closed_unmerged
  • pull_request_review_approved
  • pull_request_review_changes_requested

Each event carries provider metadata (PR number, base ref, additions/deletions, changed files) and an actor, stitched to a Halyard user via external identity when the GitHub login is linked. That stitching is what lets delivery metrics attribute work to the right person.

Connect GitHub

Section titled “Connect GitHub”
  1. In the Halyard app, go to Settings → Integrations.
  2. On the GitHub card, install the GitHub App and choose the repositories Halyard should watch.
  3. Approve the installation.

Once installed, Halyard receives webhooks for new PR and review activity going forward.

Backfill

Section titled “Backfill”

On connect, Halyard backfills the last 90 days of pull-request and review activity using the app installation token, so recent history shows up immediately rather than only events that happen after you connect.

Next

Section titled “Next”