> ## Documentation Index
> Fetch the complete documentation index at: https://docs.base44.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Push changes to GitHub

> <Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Pushes the app's latest saved version to the connected repository.

Base44 pushes each saved version by itself, whether or not [automatic sync](/api-reference/turn-automatic-github-sync-on-or-off) is on. Use this when a push failed.

The push commits the app's latest saved version on the main line, so it publishes saved work rather than the current chat [turn](/developers/references/app-management/get-started/concepts#turns), and it never pushes a Base44 branch.

A failed push is reported in the response body rather than as an error, so read `success` and `error`.

<Warning>The response includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time.</Warning>



## OpenAPI

````yaml /developers/references/app-management/app-management-openapi.json post /api/apps/{app_id}/github/sync/manual
openapi: 3.1.0
info:
  title: Base44 App Management API
  version: 1.0.0
servers:
  - url: https://app.base44.com
security:
  - PersonalAccessTokenAuth: []
paths:
  /api/apps/{app_id}/github/sync/manual:
    post:
      summary: Push changes to GitHub
      description: >-
        <Info>This API is in beta. Endpoints, fields, and behavior may still
        change, so avoid depending on it in production.</Info>


        Pushes the app's latest saved version to the connected repository.


        Base44 pushes each saved version by itself, whether or not [automatic
        sync](/api-reference/turn-automatic-github-sync-on-or-off) is on. Use
        this when a push failed.


        The push commits the app's latest saved version on the main line, so it
        publishes saved work rather than the current chat
        [turn](/developers/references/app-management/get-started/concepts#turns),
        and it never pushes a Base44 branch.


        A failed push is reported in the response body rather than as an error,
        so read `success` and `error`.


        <Warning>The response includes fields beyond the ones documented here.
        Don't rely on undocumented response fields, as they can change at any
        time.</Warning>
      operationId: trigger_manual_sync_api_apps__app_id__github_sync_manual_post
      parameters:
        - name: app_id
          in: path
          required: true
          schema:
            type: string
            description: ID of the app whose GitHub sync this affects.
            title: App Id
          description: ID of the app whose GitHub sync this affects.
          example: 6820f3a4e7b91d003c45a1f2
      responses:
        '200':
          description: The outcome of the push.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GitHubPushResult'
        '401':
          description: Missing or invalid credentials.
        '403':
          description: >-
            You don't have access to this app. The code is
            `git_sync_not_supported` when the app's type doesn't support Git
            sync.
        '404':
          description: App not found.
        '503':
          description: >-
            Database temporarily unavailable (`database_unavailable`): the data
            cluster did not answer in time. Retry after the `Retry-After`
            seconds.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StandardErrorEnvelope'
              examples:
                database_unavailable:
                  summary: database_unavailable
                  value:
                    error:
                      code: database_unavailable
                      message: Database temporarily unavailable, please retry
                      details: {}
      security:
        - PersonalAccessTokenAuth:
            - full_access
        - WorkspaceApiKeyAuth:
            - full_access
        - WorkspaceApiKeyBearerAuth:
            - full_access
components:
  schemas:
    GitHubPushResult:
      properties:
        success:
          type: boolean
          title: Success
          description: Whether the push succeeded.
          example: true
        commit_hash:
          anyOf:
            - type: string
            - type: 'null'
          title: Commit Hash
          description: Commit pushed to the repository, or `null` when nothing was pushed.
          example: 4c7e1f90ab3d5628e1a0f7b24c9d8e6350a1b2c4
        commits_pushed:
          type: boolean
          title: Commits Pushed
          description: >-
            Whether the push moved the repository forward. The value is `false`
            both when the repository already had this commit and when nothing
            was pushed at all.
          example: true
        skipped:
          type: boolean
          title: Skipped
          description: >-
            Whether the push was skipped. This is `true` for exactly one reason,
            which is that 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.
          example: false
        error:
          anyOf:
            - type: string
            - type: 'null'
          title: Error
          description: >-
            Why the push didn't happen, or `null` when it succeeded. Plain text,
            not a code you can branch on.
          example: App not connected to GitHub
        duration_ms:
          anyOf:
            - type: integer
            - type: 'null'
          title: Duration Ms
          description: >-
            How long the push took, in milliseconds, or `null` when Base44
            rejected the request before starting one.
          example: 2860
      type: object
      required:
        - success
        - commits_pushed
        - skipped
      title: GitHubPushResult
      description: Outcome of a push to the connected repository.
    StandardErrorEnvelope:
      properties:
        error:
          $ref: '#/components/schemas/StandardError'
          description: What went wrong.
      type: object
      required:
        - error
      title: StandardErrorEnvelope
      description: The error body returned in the standard envelope.
    StandardError:
      properties:
        code:
          type: string
          title: Code
          description: >-
            Stable machine-readable cause of the failure. Match on this, not on
            `message`.
          example: not_found
        message:
          type: string
          title: Message
          description: Human-readable explanation. It isn't a stable contract.
          example: App not found
        details:
          additionalProperties: true
          type: object
          title: Details
          description: >-
            Structured context for the failure, or an empty object when there's
            none.
          example: {}
      type: object
      required:
        - code
        - message
      title: StandardError
  securitySchemes:
    PersonalAccessTokenAuth:
      type: http
      scheme: bearer
      description: >-
        Personal access token, sent as `Authorization: Bearer <token>`. Each
        operation lists the permission it needs: `read_only` or `full_access`. A
        full-access token can call every operation. A read-only token can call
        only the operations that list `read_only`; anything else returns 403
        `read_only_credential_route_not_allowed`.
    WorkspaceApiKeyAuth:
      type: apiKey
      in: header
      name: api_key
      description: >-
        Workspace API key, sent as `api_key: <key>`. Each operation that accepts
        one lists what the key needs: a permission, `read_only` or
        `full_access`, like a personal access token, or a scope. A key without
        the scope gets 403 `workspace_api_key_scope_required`.
    WorkspaceApiKeyBearerAuth:
      type: http
      scheme: bearer
      description: >-
        Workspace API key, sent as `Authorization: Bearer <key>`. Accepted
        wherever `api_key` is, with the same permission.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.