starter.wiki

Developer Workflow

Git Repository Hosting

Choose a Git collaboration home by governance, deployment model, surrounding workflow, and exit requirements.

Recommendation

Start with GitHub for ordinary managed collaboration.

Choose GitLab when an integrated or self-managed DevSecOps platform is intentional, and Bitbucket when Atlassian administration is the decisive organizational constraint.12

For: Development teams selecting a hosted or self-managed Git collaboration platform

Main trade-off

A hosted Git platform removes substantial collaboration operations while concentrating identity, review history, automation hooks, packages, and migration work in one provider.123

Choose by governance and operating boundary

The repository is a durable system of record; evaluate control, workflow adjacency, and exit before add-on breadth.

  1. Governance

    Compare identity, roles, branch protection, review rules, audit, policy, enterprise administration, and data location.12

  2. Deployment model

    Decide whether managed cloud, dedicated tenancy, or self-management is an actual requirement.12

  3. Workflow adjacency

    Map issue tracking, code review, CI events, packages, security handoffs, and API or app integrations without merging their decisions.12

  4. Exit

    Test repository, issue, review, release, permission, webhook, and audit-data export and migration.12

Repository platform routes

The default changes when self-management or an established enterprise ecosystem outweighs the broad GitHub collaboration path.

A team wants the mainstream managed collaboration route

Start with GitHub.

GitHub is the bounded default for managed repositories, pull-request collaboration, and a broad developer ecosystem.

Verify: Move when self-management, consolidated GitLab operations, or Atlassian-centered administration is a hard requirement.1

Source, delivery, and governance should share GitLab

Evaluate GitLab.

GitLab is the integrated and self-managed route when repository governance belongs inside a broader DevSecOps platform.

Verify: Accept the wider platform and upgrade boundary only when consolidation or self-management is deliberate.2

Jira and Atlassian administration define the workflow

Evaluate Bitbucket.

Bitbucket is the Atlassian-centered route when repository permissions and work tracking should remain in that organizational ecosystem.

Verify: Do not choose it only for product adjacency if developer workflow, migration, or ecosystem fit is weaker.3

Boundary: CI/CD owns workflow execution and runners; Package Registry owns package publication and dependency resolution.

Official resources

Verify current product boundaries, control-plane behavior, execution limits, pricing, licensing, and operating requirements in first-party material before adoption.

Sources

Official product material supports the bounded routes and verification points; route selection remains an editorial judgment.

  1. 1
    GitHub repository documentation

    GitHub · Accessed Official

  2. 2
    GitLab repository documentation

    GitLab · Accessed Official

  3. 3
    Bitbucket Cloud repository documentation

    Atlassian · Accessed Official

  4. 4
    GitHub pricing

    GitHub · Accessed Official

  5. 5
    GitLab pricing

    GitLab · Accessed Official

  6. 6
    Bitbucket Cloud pricing

    Atlassian · Accessed Official