The GitHub Create Pull Request Tool
Create a pull request on a connected GitHub repository — head, base, title, body, reviewers — so an agent can propose changes into your normal review flow, merged by a human.
Reading isn’t doing
Most AI stops at retrieval: it can tell you what happened but can’t do anything about it. The value is in the write — creating the ticket, sending the reply, updating the record — and that demands governance, approval, and an audit trail most integrations lack.
Search-only agents
An agent that can’t act leaves every follow-up to a human.
Risky writes
Ungoverned write access to Slack, Jira, or CRM is dangerous.
Credential sprawl
Tokens scattered across tools are a breach waiting to happen.
No approval path
Consequential actions need a human gate that most bots skip.
GitHub Create Pull Request, without the risk
Capability
What it does
Open a GitHub pull request via the API.
it opens a pull request on a GitHub repository with head, base, title, body, and reviewers.
Assignable to any agent
How it works
Predictable, inspectable behavior
Designed to be reliable.
the PR is created via the GitHub API under a governed identity and enters your review and CI gates, so agent-proposed changes still require human approval to merge.
Every call logged
Governance
Private, governed, on-premise
Runs inside your perimeter.
Writes run under role-based policy with optional human approval, using credentials held in your own vault, and every action is logged — so an agent can act across your stack without over-permissioned access or data leaving your control.
Per-tenant, logged
Parameters
The github_create_pr tool accepts these inputs when an agent calls it. Required inputs are flagged.
default: main Optional Branch to merge into.
How the GitHub Create Pull Request tool works in practice
GitHub Create Pull Request is an integration & action tool you assign to a VDF AI agent. It opens a pull request on a GitHub repository with head, base, title, body, and reviewers. Its hallmarks — GitHub, Pull request, CI-gated — let an agent rely on it as a dependable step in a larger task rather than a brittle one-off script.
Under the hood, the PR is created via the GitHub API under a governed identity and enters your review and CI gates, so agent-proposed changes still require human approval to merge. It expects repo, head, and title as required inputs, so calls are explicit and easy to audit. Every call is scoped to the requesting tenant and written to an audit log, so the capability is safe to run inside a regulated, on-premise environment — the same governance model behind every VDF AI tool.
Teams reach for GitHub Create Pull Request when they need to handle propose changes, auto-description, and right reviewers. It rarely works alone — pair it with GitHub Request Review, GitHub Merge Pull Request, and GitHub Create Issue to build a complete, governed workflow, then compose those steps into an on-premise VDF AI Network.
Where GitHub Create Pull Request pays back
Propose changes
Ship agent work as a reviewable PR.
Auto-description
Generate the PR body from the diff.
Right reviewers
Request the people who should look.
Governed merge
Keep humans in control of what lands.
Assigned to agents, orchestrated as networks
On VDF AI, an industry’s use cases map to agents, and you assign tools like this one to those agents. Compose multiple agents into a governed, on-premise network.
What changes after you assign it
Questions about the GitHub Create Pull Request tool
What is the GitHub Create Pull Request tool?
It opens a pull request on a GitHub repository with head, base, title, body, and reviewers. Assigned to a VDF AI agent, it runs under role-based policy with full audit logging so the capability is safe to use in production.
How is this different from the workspace git create-PR tool?
This uses the GitHub API on any connected repo; the workspace tool drives the sandbox repo’s local Git flow.
Does the agent merge it?
No. It opens the PR; review, CI, and merge stay under human control.
What inputs does the GitHub Create Pull Request tool need?
It requires repo, head, and title, and optionally accepts base, body, and reviewers. Each parameter is validated when an agent calls the tool, and the full call is logged for audit.
Which tools pair well with GitHub Create Pull Request?
GitHub Create Pull Request is commonly assigned alongside GitHub Request Review, GitHub Merge Pull Request, and GitHub Create Issue. On VDF AI you compose several tools and agents into a single governed, on-premise network.
Does it run on-premise?
Yes. Like every VDF AI tool, it can run on-premise or in your sovereign cloud, scoped per user and audit-logged, so your data never leaves your perimeter.
How do agents use it?
You assign the tool to an agent under a role-based policy; the agent calls it as one step in a task, and several agents and tools can be orchestrated together as a governed VDF AI Network.
Assign GitHub Create Pull Request to these agents
These VDF AI agents can be assigned this tool. Open an agent to see the full toolkit it can run.
Tools that work well alongside this one
Where this tool delivers value
Put GitHub Create Pull Request to work
See the GitHub Create Pull Request tool assigned to an agent and orchestrated in a governed, on-premise network.