GitHub

GitHub is a first-class integration in Ubrella, not a developer footnote: the failed build is usually the first thing a brief mentions.

Connect

1. Settings → Integrations → GitHub → Connect.
2. GitHub asks where to install the Ubrella app: your personal account or an organisation. Choose one; repeat for each account you want — they appear as separate integrations (GitHub · olivermark, GitHub · your-org).
3. Choose All repositories or Only select repositories. Ubrella only ever reads; limiting the selection just keeps the discovery list short.

Permissions

Ubrella installs as a GitHub App with read-only permissions:

Permission	Why
Metadata (read)	list repositories
Pull requests (read)	open PRs, review state, age
Issues (read)	open issues and their labels
Actions (read)	workflow runs and their conclusions
Contents (read)	default branch name and recent commits for the timeline

No write permissions are requested. Ubrella cannot merge, comment, re-run or push.

What becomes a source

Each repository is a source. Assign it to a project — one repository per project, or several (grill-me, grill-me-api). Repositories you never assign stay unassigned and silent.

Metrics and events

Metric	Event
open pull requests	pull request opened / merged / closed
open issues	issue opened / closed (labelled critical or high)
last successful workflow run	workflow run failed / succeeded on the default branch
—	release published

Attention items

• Workflow failed on the default branch — critical; resolves when a later run of that workflow succeeds.
• No successful run after a failed one, for more than a day — critical.
• Pull request waiting for review > 3 days — attention; resolves when merged or closed.
• Issue labelled critical, high, P0 or p1 open — attention; resolves when closed.

Only the default branch counts for build state. Failures on feature branches are visible in the timeline but never open an item.

Timing

Once a day, with the morning sync. A failure at 14:00 is in tomorrow’s brief.