bitbucket_repositories
Manage Bitbucket repositories by listing, creating, deleting, forking, and accessing files to organize and control your codebase.
Instructions
Manage Bitbucket repositories. Actions:
list: List repositories in a workspace
get: Get repository details
create: Create a new repository
delete: Delete a repository
fork: Fork a repository
get_file: Get file content from a repository
list_source: List files/directories in a repository path
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Action to perform | |
| workspace | Yes | Workspace slug | |
| repo_slug | No | Repository slug (required for most actions except list) | |
| q | No | Query string to filter repositories | |
| sort | No | Sort field (e.g., "-updated_on" for newest first) | |
| role | No | Filter by role | |
| name | No | Repository display name (for create) | |
| description | No | Repository description (for create) | |
| is_private | No | Whether repository is private (for create) | |
| project_key | No | Project key to associate with (for create) | |
| new_name | No | Name for the forked repository | |
| target_workspace | No | Target workspace for the fork | |
| path | No | File or directory path in the repository | |
| ref | No | Git ref (branch, tag, or commit hash) | HEAD |
| page | No | Page number for pagination | |
| pagelen | No | Results per page (max 100) | |
| format | No | Output format: json (full), toon (compact tokens), compact (essential fields only) |