Github Commit Multiple Files

• repostring

  Required
  Repository name (without .git extension)
• forceboolean
  Force update the branch reference. WARNING: Use with caution as this can overwrite commits. Only use this when you intentionally want to overwrite the branch history.
• ownerstring

  Required
  Repository owner (username or organization name)
• authorobject
  Git author or committer information.
• branchstring

  Required
  Target branch name to commit to. If this branch doesn't exist, you MUST provide 'base_branch' to create it. For new feature branches (e.g., 'fix/my-fix', 'feature/new-feature'), always set base_branch='main' (or your default branch).
• deletesarray
  List of file paths to delete from the repository. Files must exist in the repository; attempting to delete non-existent files will result in an error. Ensure paths are exact with no leading/trailing whitespace.
• messagestring

  Required
  Commit message describing the changes
• upsertsarray
  List of files to create or update. Each entry requires path, content, and optional encoding (utf-8 or base64)
• committerobject
  Git author or committer information.
• base_branchstring
  REQUIRED when committing to a new branch that doesn't exist yet. Specifies the existing branch to create the new branch from (e.g., 'main' or 'master'). Not needed if 'branch' already exists in the repository.
• max_retriesinteger
  Maximum number of retries when encountering race conditions (422 'not a fast forward' errors). The action will refetch the HEAD and rebase changes on each retry. Set to 0 to disable retries.

• data

  Required
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  Required
  Whether or not the action execution was successful or not

No verified related use cases are linked yet.

No published Skills explicitly reference this Action yet.