Open work and failing builds for every repo.
See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch.
Connect GitHub in one click and pick the repos LopeBase can see. A fine-grained read-only token works too.
What LopeBase reads
Each property connects to one repo. LopeBase reads four things from it through GitHub's API, all about work in flight and whether the main branch builds.
- Repository summaryOpen pull requests, open issues, how many of the last 30 Actions runs failed on the default branch, the default branch's name, and when the repo was last pushed to.
- Pull requestsUp to 50 open PRs, each with its number, title, author, draft state, when it was opened, and a link.
- Actions runsThe 30 most recent workflow runs, with the workflow name, branch, result, start time, and a link to the run.
- IssuesUp to 50 open issues, with pull requests taken out, each with its author, comment count, and age.
GitHub counts open pull requests inside its open issue total. LopeBase subtracts them, so the issue count means issues.
How to connect it
Install the LopeBase GitHub app, or paste a fine-grained token. Private repos work either way.
- 01
In LopeBase, open Manage, then Connections, and pick GitHub under Infrastructure. Press Connect GitHub and install the app on the repos you choose.
- 02
LopeBase matches each repo to a property by its name and site. Check the matches and change any that are wrong.
- 03
Each property's open work and build state fill in. A failing main branch shows under Needs attention.
Prefer a token? The link in the connect guide opens GitHub's fine-grained token page with the name and read access to Contents, Pull requests, Issues, and Actions filled in. Pick the repo under Repository access, generate it, and paste it with the repo as owner/name. See Connect your tools.
What LopeBase does with it
For status, LopeBase only reads pull requests, issues, and Actions runs. It never merges anything, and it only writes to a repo if you turn on publishing below.
- Failing buildsIf the latest run of a workflow on the default branch failed or timed out, the property is flagged, with the workflow names. A failure that a later run fixed is history, not a problem.
- On the timelineFailed runs on the main branch, and passing runs of workflows named for deploys or releases, land on each property's 30-day timeline next to error spikes and outages.
- AlertsA failing build counts under Builds and errors in your alert settings, by email or browser push.
- A broken connectionIf the app is removed from a repo or a token expires, the connection shows under Needs attention, so a gap in the numbers never goes unnoticed.
Publishing articles as pull requests
If your blog lives in the repo, the content autopilot can send approved articles there. You choose this yourself, per property, under Content.
- One PR per articleAn approved article is written as a Markdown file on a new branch, and LopeBase opens a pull request. Merge it to publish.
- Edits come the same wayChange a published article in LopeBase and it opens another pull request with the update.
- Write access only for thisWith the app, each call gets a fresh token for one repo. Status reads use read permissions; only publishing asks for write to contents and pull requests.
Set it up in Content. A token you paste for status stays read-only and is never used to publish; publishing goes through the app, or a token you add on the Content destination itself.
Questions it answers
Across several products, the question is rarely about one repo. It is where work is stuck.
- Is any main branch red?Every property with a failing workflow, named, on Overview.
- Where are PRs piling up?Open and draft pull requests per repo, with their age, so a stale branch stands out.
- Did a deploy cause the error spike?With Sentry or another error tracker on the same property, the deploy and the spike share a timeline.
- Is the Worker the problem, or the build?Pair it with Cloudflare for Worker error rates and the latest deploy per Worker.
- Can my agent see it?Over MCP, get_health lists failing builds with every other failing check. See the MCP server.
What it does not do
- No merging or re-runsMerge, close, and re-run in GitHub.
- One repo per propertyA product spread over several repos connects its main one.
- Recent runs onlyBuild state comes from the last 30 runs, so a workflow that has not run in a long while may not show.
- Counts stop at 50Open PRs and issues are read 50 at a time, which is the most the summary counts.
GitHub questions
Something else? Contact us.
Can I merge or re-run builds from LopeBase?
Not today. The GitHub connector reads. Merge and re-run in GitHub.
Does it work with private repos?
Yes. LopeBase sees the repos you add to its GitHub app, or that your token can read.
Which permissions does a token need?
Read access to contents, pull requests, issues, and Actions. The link in the connect guide fills them in for you.
Does LopeBase store a GitHub token when I use the app?
No. It keeps only the app installation, sealed, and asks GitHub for a token for one repo each time it reads. Those tokens last about an hour.
Which branch does it watch?
The repo's default branch, as GitHub reports it. Failures on other branches show in the runs table but do not flag the property.
Can it publish my blog posts?
Yes, if you pick a GitHub pull request as the property's Content destination. Each approved article becomes a pull request that you merge.
Put GitHub next to everything else.
Free for one property. No card.