GitHub Propose a Change via Pull Request
Version 1.0.0
Branch, commit a file, and open a pull request back to the base branch.
1 workflow
3 source APIs
1 provider
propose-change-pull-request
Create a branch, commit a file, then open a pull request for it.
Resolves the base branch SHA, creates a branch, commits a file, and opens a pull request from the new branch to the base branch.
4 steps
inputs: baseBranch, contentBase64, githubToken, message, newBranch, owner, path, prBody, prTitle, repo
outputs: newRef, pullNumber, pullUrl
1
getBaseRef
Read the base branch reference to obtain its commit SHA.
2
createBranchRef
Create the new branch reference from the base commit SHA.
3
commitFile
Commit the file onto the new branch.
4
openPullRequest
Open a pull request from the new branch back to the base branch so the committed change can be reviewed.
Every workflow here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for arazzo workflows
4 MCP tools reach this
find_arazzoBrowse and filter every workflow in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/github-propose-change-pull-request-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.