Push changes to GitHub
Pushes the app’s latest saved version to the connected repository.
While automatic sync is on Base44 pushes each saved version by itself, so reach for this when a push failed or when you have turned automatic sync off: it pushes either way. It commits the app’s latest saved version on the main line, so it publishes saved work rather than the current chat turn, and it never pushes a branch.
success: true with commits_pushed: false means the repository already had that commit, so there was nothing new to send.
Authorizations
Personal API key.
Path Parameters
ID of the app whose GitHub sync this affects.
Response
The outcome of the push.
Outcome of a push to the connected repository.
Whether the push succeeded.
true
true when the push moved the repository forward. false both when the repository already had this commit and when nothing was pushed at all.
true
true for exactly one reason: the connection carries no GitHub App installation. Every other reason nothing was pushed comes back false, including no connection at all and a connection in error or revoked, so read error rather than this flag.
false
Commit pushed to the repository, or null when nothing was pushed.
"4c7e1f90ab3d5628e1a0f7b24c9d8e6350a1b2c4"
Why the push didn't happen, or null when it succeeded. Plain text, not a code you can branch on.
"App not connected to GitHub"
How long the push took, in milliseconds. null when Base44 rejected the request before starting one.
2860