oriz.in / knowledge
type: service
status: active
timestamp: 2026-06-24
tags: [service, git-host, mirror, backup, bitbucket, atlassian, free-tier]

Bitbucket Cloud — push-mirror target for chirag127 + chirag127

Git mirror host #3 — unlimited private repos, 1 GB storage, push via GH Actions

Bitbucket Cloud — push-mirror target

Role

Bitbucket Cloud (Atlassian) is mirror host #3 in the 6-host DR strategy. Provides Atlassian-backed geographic + corporate diversity. Free, unlimited private repos, 1 GB workspace total storage.

⚠️ CRITICAL: App Passwords DEPRECATED July 28 2026

Bitbucket App Passwords are being permanently removed.

Any existing BITBUCKET_APP_PASSWORD entries in mirror-all.yml MUST be replaced with MIRROR_BITBUCKET_API_TOKEN (Workspace Access Token).

See setup steps below for the new token type.

Free Tier

LimitValue
ReposUnlimited private repos
Workspace storage1 GB total (all repos combined; read-only if exceeded)
Users5 per workspace (Free)
CI Pipelines50 min/month
Inactive reposMay be archived after 3 months of no push activity
SnippetsRemoved from Free tier
Pull mirroring❌ No native pull-mirror from GitHub

Our repos are < 10 MB each; 1 GB workspace is ample for 60+ repos.

Authentication (NEW — Workspace Access Token)

FieldValue
Token typeWorkspace Access Token (formerly App Password — deprecated)
Token URLWorkspace settings → Security → Access tokens
Direct URLhttps://bitbucket.org/account/settings/access-tokens/
Required permissionsRepositories: Write, Projects: Read
Env var namesMIRROR_BITBUCKET_API_TOKEN, MIRROR_BITBUCKET_USERNAME
Git URL formathttps://USERNAME:TOKEN@bitbucket.org/workspace/repo.git
API Auth headerAuthorization: Bearer TOKEN

How to get a Workspace Access Token

  1. Log in at https://bitbucket.org
  2. Go to your workspace settings: https://bitbucket.org/account/settings/access-tokens/ (Or: Workspace → Settings → Security → Access tokens)
  3. Click Create access token
  4. Name: oriz-mirror-bot
  5. Permissions: Repositories — Write + Projects — Read
  6. Expiry: set 1 year from today
  7. Click Create — copy immediately, shown once
  8. Store as chirag127 org-level GitHub secret(s) — paste value into .env then gh secret set <NAME> --org chirag127 --visibility all < <(printf %s "$VALUE"). Full loop: runbooks/platform/mirror-all-hosts-setup.md Step 2.

API — Create Repo (idempotent)

# Create repo in workspace
curl -s -X POST \
  -H "Authorization: Bearer ${MIRROR_BITBUCKET_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d "{\"scm\":\"git\",\"is_private\":true,\"description\":\"Mirror of github.com/chirag127/${REPO_NAME}\"}" \
  "https://api.bitbucket.org/2.0/repositories/${MIRROR_BITBUCKET_USERNAME}/${REPO_NAME}" \
  || true  # 400/409 = already exists — fine

API docs: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/

Rate Limits

No documented hard rate limit for the API; standard Atlassian fair-use applies. Add sleep 0.5 between creation calls in loops to be safe.

Pull Mirror — NOT available

Bitbucket has no native pull-mirror feature for importing from GitHub. We use GitHub Actions push-mirror only.

Mirror URL pattern

https://${MIRROR_BITBUCKET_USERNAME}:${MIRROR_BITBUCKET_API_TOKEN}@bitbucket.org/${MIRROR_BITBUCKET_USERNAME}/${REPO_NAME}.git

Failure modes

SymptomCauseFix
401 UnauthorizedOld App Password usedGenerate Workspace Access Token
403 ForbiddenToken missing Repositories: Write scopeRegenerate with correct permissions
404 Not Found on pushMirror repo not pre-createdRun repo-creation script
Workspace storage > 1 GBToo many large reposRemove LFS objects or upgrade plan
Repo archived (inactivity)No push for 3+ monthsPush a dummy commit to un-archive

Cross-refs

Edit on GitHub · Back to index