osFoundry / Platform
Pull requests
A workspace-wide PR dashboard. CI status, reviewers, conflicts — everything at a glance.
What it is
Pull requests is the code-review dashboard inside osFoundry's Code & Build area. Instead of tabbing between repositories to find out which PRs are green, who still owes a review, and what is blocked on a conflict, you get one workspace-wide list that pulls the signals you actually decide on to the surface: CI status, requested and completed reviewers, and merge conflicts. It answers the question a maintainer asks a dozen times a day — "what is ready, and what is stuck?" — without opening each PR one at a time.
Because osFoundry runs as a local-first desktop workspace, the dashboard lives alongside your chat, agents, code, knowledge, and data rather than in a separate browser tab. The same window where you read a PR is the window where you can ask an AI model to summarize the diff, draft a review comment, or explain why a check failed — and that model is whichever one you connect, local, cloud, or self-hosted, on your own API key with no reseller markup. Nothing about the code or the review has to leave your machine to get an at-a-glance view.
It matters because review latency is where most teams lose time, and the cause is usually visibility, not effort. A PR sits green and mergeable for two days because no one noticed; another blocks a release because its conflict was never surfaced. Putting CI, reviewers, and conflicts in a single ranked view turns "go hunting" into "glance and act," and keeps that view in the same place you already work rather than behind another login and another per-seat bill.
Key capabilities
- See every open pull request across your workspace in one list, without opening repos one at a time
- Read CI status at a glance so you know which PRs are green and mergeable and which are failing checks
- Track reviewers per PR — who was requested, who has approved, and what is still waiting on a review
- Spot merge conflicts early instead of discovering them at merge time or during a release
- Review right inside your local-first desktop workspace, next to chat, agents, code, and data — using your own AI model and API key
Use cases
- Maintainer: opens the dashboard each morning to find PRs that are green and reviewed, and merges them without hunting through repositories
- Team lead: scans reviewer columns to see which pull requests are waiting on a review and nudges the right person
- Release manager: catches PRs with merge conflicts before cutting a release, instead of hitting them mid-merge
Frequently asked questions
Does the dashboard show pull requests from more than one repository?
Yes. It is a workspace-wide view, so open PRs across the repositories in your workspace appear in a single list rather than one repo at a time. That is the point of the dashboard — one place to see everything instead of tabbing between repos.
What can I see about each pull request at a glance?
The three signals you usually act on: CI status (is it passing), reviewers (who was requested, who approved, what is still pending), and merge conflicts (whether it can merge cleanly). The goal is to tell what is ready and what is blocked without opening each PR.
Do I need a separate subscription or per-seat fee to use it?
No. Pull requests is part of the osFoundry desktop workspace, which is bring-your-own-key and has no per-seat fees. Any AI help you use on a PR runs on the model and API key you connect — local, cloud, or self-hosted — with no reseller markup, and your code can stay on your device.