GitHub
Approved technical actions become draft GitHub pull requests — diff preview, affected files, risk level, and a rollback note. You review and merge; BIU never auto-merges.
What data flows
Exactly what BIU reads or writes for this connection — so you can judge the data exchange before you connect, not after.
- Repository context BIU needs to scope a fix — files and structure for the change.
- The proposed change itself, surfaced as a diff you can review line by line.
- Writes: a draft pull request you open and merge — never a direct push to a branch.
- Access is scoped to the repositories you connect, nothing more.
Permissions you grant
The access this connection requests — scoped, and revocable whenever you choose.
- Scoped access to the specific repositories you authorize.
- BIU opens draft pull requests only — it never auto-merges or force-pushes.
- You review every PR through your normal process and merge it yourself.
How to connect
A short setup — most of the value comes from analyzing your site first, then connecting to sharpen it.
- 1
Connect a repository
You authorizeAuthorize BIU for the specific repositories where approved technical actions should ship. Scope stays limited to what you select.
- 2
Approve a technical action
In BIUWhen an SEO or technical action is ready, approve it. BIU prepares the change with a diff preview, affected files, risk level, and a rollback note.
- 3
Review and merge the PR
You mergeBIU opens a draft pull request. You review it like any other PR and merge it yourself — there is no auto-merge and no silent change.
Sync cadence
Pull requests are created on demand when you approve a technical action — BIU does not run background commits or modify code without an approval.
Actions this unlocks
What connecting adds to your queue — sharper ranking, attribution, or new kinds of Growth Action.
- Technical fixes (metadata, structured data, broken links) shipped as reviewable PRs.
- A clear audit trail: diff, affected files, risk level, and a one-line rollback note per change.
- Safe execution for dev-tools and engineering-led teams — your review gate is never bypassed.
Privacy and data handling
GitHub access is scoped to the repositories you connect. BIU reads only what it needs to prepare a fix and writes only draft pull requests you review and merge — it never force-pushes, auto-merges, or changes code silently.
Troubleshooting
The most common setup snags and how to clear them.
The pull request didn't open.
Confirm BIU is authorized for that repository and that branch protections allow a PR. Re-authorize the specific repo if its access was removed.
I want changes on a specific branch.
BIU targets a review branch and opens a PR into your default branch. Configure your preferred base branch in the integration settings before approving the action.
Keep exploring
BIU turns an approved technical action into a draft GitHub pull request — affected files, diff preview, risk level, and rollback note. You review and merge; BIU never auto-merges or changes code silently.
Take metadata, structured-data, and broken-link issues from diagnosis to a draft GitHub pull request with a diff, risk level, and rollback note. You review and merge — BIU never edits code silently.
Grow a dev tool with an engineer-friendly voice — substance-first HN and Reddit, technical SEO and GEO, and approved technical fixes that ship as reviewable GitHub PRs. No silent code changes.
How BIU reads public pages, handles your data, requests approval before any external action, and the model providers and controls behind the product.
Integrations are optional — BIU starts from your URL alone, and connecting only sharpens ranking and attribution. See pricing for what each plan includes.
GitHub — questions
Can BIU merge code on its own?
No. BIU only opens draft pull requests with a diff, risk level, and rollback note. You review and merge through your normal process — there is no auto-merge.
What repository access does it need?
Scoped access to just the repositories you connect. It reads what it needs to prepare a fix and writes only the pull requests you approve.
Can I roll back a change?
Yes. Every PR includes a rollback note, and because changes ship as standard pull requests, reverting uses your normal Git workflow.
Turn your website into today's growth actions
Enter your URL and BIU builds your company memory, then finds, drafts, and ranks the work — you approve what ships.