Tool to list commits from a revision using POST method. Identical to GET endpoint but allows sending include/exclude parameters in request body to avoid URL length limits. Use when include/exclude parameters are too long for query strings.
pageintegerPage number for paginated results (starts from 1).
pathstringOptional file path to filter commits. Only commits that modified this file or directory will be returned.
excludestringOptional commit hash or branch to exclude from the results. Can be used to create a range with the 'include' parameter. Use POST method when this value is very long.
includestringOptional commit hash or branch to include in the results. Can be used to create a range with the 'exclude' parameter. Use POST method when this value is very long.
pagelenintegerNumber of commits per page (1-100). Bitbucket default is typically 30 if not specified.
revisionRequiredstringThe commit hash, branch name, tag, or other revision identifier to start listing commits from. Commits are returned in reverse chronological order starting from this revision.
repo_slugRequiredstringThe slug of the repository. This is the repository's name, usually in lowercase and with hyphens instead of spaces.
workspaceRequiredstringThe workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier.
dataRequiredData from the action execution
errorstringError if any occurred during the execution of the action
successfulRequiredbooleanWhether or not the action execution was successful or not
OAuth connection. Risk level 2 of 5.
Free Action
No published Skills explicitly reference this Action yet.