GitHub

The GitHub integration gives your pipelines a read of development activity: commits, pull requests, reviews, and continuous integration status — by repository and by developer.

What you can do with it

• Team output report — who shipped what over the period, PR volume, review turnaround.
• CI health — status of the latest deployments / workflows, failures to flag.
• Feed a CTO IA — an agent that summarizes the technical week (see Use cases → CTO IA).

Connection (BYO)

1. Administration → Integrations → GitHub.
2. Enter a GitHub access token with the required read scopes (ideally a fine-grained PAT limited to the relevant repositories).
3. The token is encrypted at rest and never re-exposed.

The github_report node

The github_report node fetches activity over a time window and publishes it into the context, broken down by developer and by repository. A downstream agent turns it into a readable report.

Best practices

• Prefer a dedicated token for the integration over a shared personal token.
• Restrict scopes to the strict minimum (read access to repositories and actions).
• Combine with the Schedule channel for a recurring report (e.g. every evening at 6pm).