Skip to content
ProductArena

Code Hosting Arena

GitHub vs Bitbucket

GitHub logo

GitHub

GitHub (Microsoft)

Arena44/100AGENT-READY71/100BUILT-IN AI80/100
MCP✓CLI✓API✓
free-tier0/100 integrity
Bitbucket logo

Bitbucket

Atlassian

Arena14/100AGENT-READY19/100BUILT-IN AI27/100
MCP✓CLI~API—
free-tier10/100 integrity

GitHub wins · 35–19 (17 drawn)

Agenticness — how well agents can access and operate the productAgenticness

How well agents can access and operate the product

Agent access

  1. ai-native userPoint an agent at llms.txt or agent-oriented docs

    weight 2 · round to GitHub
    GitHubfullprobed8/10

    A live probe confirms GitHub Docs serves a working llms.txt file at https://docs.github.com/llms.txt (HTTP 200) with a structured description of GitHub as a developer platform, which is exactly the agent-oriented docs entry point the story describes. Missing for 10: no independent third-party confirmation of agents actually consuming this file, and no broader agent-oriented docs index beyond the single llms.txt endpoint.

    • [probe] “PROBE llms.txt: HTTP 200 at https://docs.github.com/llms.txt # GitHub Docs > GitHub is a developer platform for building, shipping, and mai…”
    proof ↗⚑ flag
    Bitbucketnone0/10

    Direct probes for llms.txt, markdown docs, and OpenAPI specs all returned 404s, and no evidence shows Bitbucket/Atlassian publishing agent-oriented docs like llms.txt.

    • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
    • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
    • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
    proof ↗⚑ flag

  2. ai-native userRun the product headlessly / in CI for automation

    weight 2 · round to GitHub
    GitHubfullprobed8/10

    GitHub Actions is explicitly documented as CI/CD automation running in the repository, and GitHub CLI/REST/GraphQL APIs support headless scripting and automation outside any UI, corroborated by an official CLI and probe confirmation. missing for 10: independent/hands-on evidence of Copilot agent tasks running fully headlessly in CI pipelines beyond Actions/CLI docs.

    • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
    • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
    • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
    • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line.”
    • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
    • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
    • [probe] “official CLI documented at https://cli.github.com/”
    proof ↗⚑ flag
    Bitbucketfullclaimed7/10

    Bitbucket ships a native CI/CD system (Pipelines) that runs headlessly with hosted or private runners and 'no infrastructure needed,' and explicitly supports triggering AI-powered automated workflows (cleanup, docs, release notes, flaky-test fixes) from the pipeline. This directly satisfies running the product headlessly/in CI for automation. missing for 10: independent/hands-on corroboration of Pipelines reliability and any CLI-level headless invocation outside the pipeline UI.

    • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
    • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
    • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
    proof ↗⚑ flag

  3. ai-native userPlug MCP servers into this product so it can use their tools

    weight 3 · round to GitHub
    GitHubfullclaimed8/10

    GitHub Copilot Chat explicitly supports connecting external MCP servers to extend its context and tools, documented with setup instructions for IDE integration (github-docs-28, github-docs-29, github-docs-30). This directly matches the story of plugging MCP servers into the product so it can use their tools. Missing for 10: independent/hands-on user reports confirming real-world reliability of third-party MCP server connections, and broader detail on limitations across non-IDE surfaces (e.g., github.com web chat vs IDE only).

    • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
    • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
    • [claimed-docs] “The GitHub MCP server in Visual Studio Code can be configured remotely or locally.”
    proof ↗⚑ flag
    Bitbucketnone0/10

    The only MCP-related evidence found is Atlassian's own MCP server (bitbucket-probe-4), meaning Bitbucket exposes tools via MCP rather than allowing users to plug external MCP servers into Bitbucket so it can use their tools. No evidence shows Bitbucket/Rovo acting as an MCP client that can consume third-party MCP servers.

    • [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
    • [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
    proof ↗⚑ flag

  4. ai-native userConnect an agent via an official MCP server

    weight 3 · round to GitHub
    GitHubfullprobed9/10

    GitHub ships and documents an official GitHub MCP server (github-probe-3: github/github-mcp-server) that lets AI agents interact with repositories, issues, and PRs, with detailed setup docs for local/remote configuration in VS Code (github-docs-29, github-docs-30) and integration guidance for connecting MCP servers to Copilot Chat (github-docs-28). This is a first-party, well-documented server-side MCP offering rather than just client-side MCP consumption. Missing for 10: independent/hands-on community corroboration of the MCP server working reliably in third-party agent setups.

    • [probe] “official MCP server documented at https://github.com/github/github-mcp-server”
    • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
    • [claimed-docs] “The GitHub MCP server in Visual Studio Code can be configured remotely or locally.”
    • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
    proof ↗⚑ flag
    Bitbucketfullprobed7/10

    There is direct evidence of an official Atlassian MCP server repository (atlassian-mcp-server), which covers Bitbucket as part of the Atlassian suite, enabling agents to connect via MCP. However, the evidence pack lacks detailed documentation on Bitbucket-specific MCP setup, tool scope, or independent hands-on confirmation. Missing for 10: first-party Bitbucket docs describing MCP server usage, independent verification of the server's functionality with Bitbucket specifically.

    • [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
    proof ↗⚑ flag

  5. ai-native userUse an official CLI

    weight 2 · round to GitHub
    GitHubfullprobed9/10

    GitHub ships both the official GitHub CLI (gh) for repo/workflow operations and a dedicated Copilot CLI for AI-native terminal use, both with first-party docs and install instructions across platforms. missing for 10: independent/hands-on third-party review specifically validating the CLI tools (community evidence in the pack is about unrelated topics, not the CLI).

    • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
    • [claimed-docs] “You can install Copilot CLI using WinGet (Windows), Homebrew (macOS and Linux), npm (all platforms), or an install script (macOS and Linux).”
    • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
    • [claimed-docs] “Enter `gh repo clone OWNER/REPO`. For example, `gh repo clone octo-org/octo-repo` clones the `octo-org/octo-repo`”
    • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line.”
    • [probe] “official CLI documented at https://cli.github.com/”
    proof ↗⚑ flag
    Bitbucketpartialclaimed4/10

    Docs mention Rovo being accessible 'in your terminal or in your IDE,' implying some CLI-based AI access, but there's no dedicated documentation of an official Bitbucket CLI tool, its command set, or installation/usage details. missing for 10: dedicated official CLI product docs, command reference, installation instructions, independent corroboration of CLI usage.

    • [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
    proof ↗⚑ flag

  6. ai-native userDrive the product through a documented public API

    weight 3 · round to GitHub
    GitHubfullprobed9/10

    GitHub documents both a REST API (with fine-grained token permissions) and a GraphQL API for creating integrations, retrieving data, and automating workflows, plus SDK-adjacent tools like the official CLI and MCP server for programmatic access. This is exactly the kind of documented public API surface an AI-native user would drive automation through. Missing for 10: a discoverable machine-readable OpenAPI spec (probe found 404s on standard OpenAPI paths) and independent hands-on developer corroboration of API usability.

    • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
    • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
    • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
    • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
    • [probe] “official MCP server documented at https://github.com/github/github-mcp-server”
    • [probe] “official CLI documented at https://cli.github.com/”
    • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
    proof ↗⚑ flag
    Bitbucketnone0/10

    The evidence pack contains no documentation or reference to a public Bitbucket REST/GraphQL API; the only related probes (llms.txt, docs.md, OpenAPI spec) all returned 404s, and no other citation mentions an API for programmatic control. While a documented API is a plausible axis for an SCM/CI platform, this pack provides no confirming evidence.

    • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
    • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
    • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
    proof ↗⚑ flag

  7. ai-native userIssue scoped/least-privilege API credentials for an agent

    weight 2 · round to GitHub
    GitHubfullclaimed7/10

    GitHub's fine-grained personal access tokens let a user grant a specific, minimal set of permissions per resource, and the REST API even returns an X-Accepted-GitHub-Permissions header showing exactly what scope is required for an endpoint — a direct implementation of least-privilege credentialing that any automated actor (including an agent) can use to authenticate to the API. Missing for 10: explicit documentation tying fine-grained PAT/GitHub App scoping specifically to Copilot/agent workflows (e.g., an agent-specific token-issuance flow) and independent hands-on confirmation.

    • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
    • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
    • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions.”
    • [claimed-docs] “Permissions define what resources the token can access via the API.”
    proof ↗⚑ flag
    Bitbucketnone0/10

    Evidence shows only general workspace/repo/branch permission controls (bitbucket-docs-9) but nothing about issuing scoped or least-privilege API credentials/tokens specifically for an AI agent, such as app passwords or API token scopes tied to agent use cases.

    • [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
    proof ↗⚑ flag

  8. ai-native userBuild against official SDKs

    weight 2 · round to GitHub
    GitHubpartialprobed5/10

    GitHub documents official REST and GraphQL APIs plus authentication mechanisms (fine-grained PATs, permissions) that developers can build against, and provides a CLI and MCP server for programmatic access, but the evidence pack never names or links an official SDK (e.g., Octokit) for any language, nor SDK-specific docs, versioning, or install instructions. missing for 10: explicit official SDK libraries, language-specific package docs/installation, and SDK versioning/support guarantees.

    • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
    • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
    • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
    • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
    • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
    • [probe] “official MCP server documented at https://github.com/github/github-mcp-server”
    • [probe] “official CLI documented at https://cli.github.com/”
    proof ↗⚑ flag
    Bitbucketnone0/10

    The evidence pack contains no mention of official SDKs for building against Bitbucket/Atlassian APIs, and the probes explicitly show 404s for openapi/API-schema and machine-readable docs endpoints, indicating no discoverable SDK or API spec was found. Only an MCP server is documented, which addresses a different story, not SDK access.

    • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
    • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
    • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
    proof ↗⚑ flag

  9. ai-native userSubscribe to events via webhooks

    weight 2 · round drawn
    GitHubnone0/10

    The evidence pack covers GitHub Copilot, CLI, REST/GraphQL APIs, MCP servers, and marketplace integrations, but contains no documentation or mention of GitHub's webhooks feature or event subscription mechanism for AI-native/agentic use. Although webhooks are a well-known GitHub capability, none of the provided citations reference them, so this applicable axis has no supporting evidence.

      ⚑ flag
      Bitbucketnone0/10

      The evidence pack contains no mention of webhooks or event subscription APIs for Bitbucket; docs cover Jira integration, AI code review, CI/CD, security, and permissions but not webhook support, which is a well-known Bitbucket capability but unevidenced here.

        ⚑ flag

      Agentic features

      1. ai-native userGet AI-generated insights and suggestions from my data inside the product

        weight 2 · round to GitHub
        GitHubfullcommunity8/10

        GitHub Copilot generates AI-driven insights and suggestions directly from a user's own codebase: it reviews code changes with actionable suggested fixes (github-docs-25), autofixes vulnerabilities (github-docs-5, github-docs-14), and in Agent/Ask mode analyzes the repository to explain and generate needed edits (github-docs-13, github-docs-56). Independent hands-on comments confirm suggestions can closely match developer intent (github-comm-11). Missing for 10: independent verification of accuracy/insight quality beyond code suggestions (e.g., non-code data insights like issue/PR analytics) and more third-party validation of Autofix/code-review reliability.

        • [claimed-docs] “Apply fixes in seconds. Spend less time debugging and more time building features with Copilot Autofix.”
        • [claimed-docs] “The user switches from 'Ask' mode to 'Agent' mode from a dropdown menu, then sends the prompt 'Update the website to allow searching for run…”
        • [claimed-docs] “Leverage security campaigns and Copilot Autofix to reduce application vulnerabilities.”
        • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
        • [claimed-docs] “It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.”
        • [community] “Early Copilot user reports: 'Copilot guesses the exact code I want to write about one in ten times... when it guesses right, it feels like i…”
        proof ↗⚑ flag
        Bitbucketpartialclaimed6/10

        Bitbucket docs claim AI code review that reviews changes and suggests fixes, plus Rovo-powered AI workflows and model access, indicating AI-generated insights/suggestions from repository data. However, these are vendor claims with no independent/hands-on corroboration, and community evidence is silent on AI features entirely. Missing for 10: independent verification of AI review quality, concrete examples of AI-generated insights in practice, and detail on how deeply Rovo integrates with actual code/data.

        • [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
        • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
        • [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
        proof ↗⚑ flag

      2. ai-native userSet up automations that run autonomously in the background

        weight 2 · round to GitHub
        GitHubfullclaimed8/10

        GitHub Actions provides scheduled/event-triggered workflows that run autonomously in the background, and Copilot cloud agent can be assigned tasks that research, plan, and implement changes asynchronously without live supervision, with a centralized dashboard to track sessions. missing for 10: independent/hands-on validation of long-running autonomous agent reliability and more detail on failure/error handling in unattended runs.

        • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
        • [claimed-docs] “Copilot can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and c…”
        • [claimed-docs] “Copilot cloud agent can: * Research a repository * Create implementation plans * Fix bugs * Implement incremental new features * …”
        • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
        • [claimed-docs] “This quickstart shows how to ask questions about code and assign a coding task to Copilot cloud agent. It takes about ten minutes.”
        proof ↗⚑ flag
        Bitbucketpartialclaimed5/10

        Bitbucket documents AI-triggered pipeline automations (cleanup, docs updates, release notes, flaky test fixes) that run 'all from your pipeline,' suggesting background autonomous execution, but there is no detail on scheduling, triggers, or true autonomy without human initiation, and no independent/hands-on corroboration. Missing for 10: concrete documentation of trigger conditions/scheduling for autonomous runs, evidence of unattended multi-step agentic execution, and third-party confirmation the feature works as described.

        • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
        • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
        proof ↗⚑ flag

      3. ai-native userDelegate tasks to a built-in AI assistant inside the product

        weight 3 · round to GitHub
        GitHubfullclaimed8/10

        GitHub Copilot is built directly into GitHub and supports true task delegation: switching to 'Agent' mode to have Copilot plan and execute multi-file changes, a cloud agent that can research a repo, create implementation plans, fix bugs and open PRs, custom specialized agents, and assigning PR reviews or mobile tasks to Copilot (github-docs-2,13,26,48,55,9,4,27,46). This goes well beyond simple autocomplete into genuine agentic delegation of work. missing for 10: independent/hands-on evidence specifically validating the delegation-to-agent workflow (community evidence only covers basic code-suggestion quality, not agent-mode task delegation).

        • [claimed-docs] “The user switches from 'Ask' mode to 'Agent' mode from a dropdown menu, then sends the prompt 'Update the website to allow searching for run…”
        • [claimed-docs] “The user switches from 'Ask' mode to 'Agent' mode from a dropdown menu, then sends the prompt 'Update the website to allow searching for run…”
        • [claimed-docs] “Copilot can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and c…”
        • [claimed-docs] “Copilot cloud agent can: * Research a repository * Create implementation plans * Fix bugs * Implement incremental new features * …”
        • [claimed-docs] “This quickstart shows how to ask questions about code and assign a coding task to Copilot cloud agent. It takes about ten minutes.”
        • [claimed-docs] “Assign initial reviews to Copilot for greater speed and quality.”
        • [claimed-docs] “Manage projects and assign tasks to Copilot, all from your mobile device.”
        • [claimed-docs] “You can create specialized agents with tailored expertise for specific development tasks.”
        • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
        • [claimed-docs] “It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.”
        proof ↗⚑ flag
        Bitbucketpartialclaimed6/10

        Bitbucket docs mention built-in AI capabilities: an AI code reviewer that reviews changes and suggests fixes, AI-powered pipeline workflows to automate tasks (feature flag cleanup, docs updates, release notes, flaky test fixes), and access to Rovo AI assistant in terminal/IDE. These support delegating tasks to a built-in AI assistant, but the story's depth (e.g., detailed task delegation UX, chat-based commands) isn't well documented and there is no independent/hands-on corroboration of these AI features actually working. Missing for 10: independent verification of AI assistant behavior, deeper documentation of delegation workflow, and community evidence confirming real-world use.

        • [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
        • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
        • [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
        proof ↗⚑ flag

      4. ai-native userOperate the product with natural-language commands

        weight 2 · round to GitHub
        GitHubfullclaimed8/10

        GitHub Copilot (Chat, Agent mode, CLI, and cloud agent) lets users issue natural-language prompts like 'Update the website to allow searching for running races by name' and have Copilot plan and implement changes, and Copilot CLI brings this to the terminal directly (github-docs-2, 13, 23, 26, 48, 55). This is well documented across multiple first-party surfaces (IDE, CLI, cloud agent, mobile task assignment). missing for 10: independent hands-on evidence validating reliability of NL-driven agent actions at scale, and clearer detail on limitations/failure modes of natural-language commands.

        • [claimed-docs] “The user switches from 'Ask' mode to 'Agent' mode from a dropdown menu, then sends the prompt 'Update the website to allow searching for run…”
        • [claimed-docs] “The user switches from 'Ask' mode to 'Agent' mode from a dropdown menu, then sends the prompt 'Update the website to allow searching for run…”
        • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
        • [claimed-docs] “Copilot can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and c…”
        • [claimed-docs] “Copilot cloud agent can: * Research a repository * Create implementation plans * Fix bugs * Implement incremental new features * …”
        • [claimed-docs] “This quickstart shows how to ask questions about code and assign a coding task to Copilot cloud agent. It takes about ten minutes.”
        • [claimed-docs] “It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.”
        • [claimed-docs] “GitHub Copilot is built into GitHub, so you can use it without installing anything.”
        proof ↗⚑ flag
        Bitbucketnone0/10

        Evidence shows AI code review, AI-triggered pipeline workflows, and Rovo access in terminal/IDE, but nothing indicates Bitbucket itself can be operated via natural-language commands (e.g., chat-based repo management, NL-driven PR/merge actions). Missing for 10: any documentation of natural-language command interface, conversational control of Bitbucket actions, or hands-on evidence of NL-driven operation.

        • [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
        • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
        • [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
        proof ↗⚑ flag

      Api quality

      1. ai-native userExplore an interactive API reference with runnable examples

        weight 2 · round drawn
        GitHubnone0/10

        Evidence shows GitHub has REST and GraphQL API documentation (github-docs-40,41,51) and permission references (github-docs-18,19,21,42), but nothing describes an interactive reference with runnable/try-it examples, and the probe for a discoverable OpenAPI spec returned 404s across all candidate paths (github-probe-2), suggesting no machine-readable interactive spec is exposed.

        • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
        • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
        • [claimed-docs] “The GitHub GraphQL API offers flexibility and the ability to define precisely the data you want to fetch.”
        • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
        • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
        proof ↗⚑ flag
        Bitbucketnone0/10

        No evidence of an interactive API reference or runnable examples; probes for OpenAPI/docs-md/llms.txt all returned 404s, indicating no such interactive reference is exposed.

        • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
        • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
        • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
        proof ↗⚑ flag

      2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

        weight 2 · round drawn
        GitHubnone0/10

        While GitHub documents its REST and GraphQL APIs (github-docs-40/41), the evidence pack shows an explicit probe for a machine-readable OpenAPI/Swagger spec at all standard paths (openapi.json, swagger.json, etc.) returning 404, with no alternate documented location for a downloadable spec.

        • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
        • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
        • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
        proof ↗⚑ flag
        Bitbucketnone0/10

        Probes explicitly show no OpenAPI/swagger spec found at Bitbucket's/Atlassian's support domain, and no docs evidence mentions a downloadable machine-readable API spec.

        • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
        • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
        • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
        proof ↗⚑ flag

      3. ai-native userTest against a sandbox environment without touching production data

        weight 1 · round to GitHub
        GitHubpartialclaimed3/10

        GitHub Codespaces offers a 'full, cloud-based development environment' (github-docs-3) that could serve as an isolated sandbox for coding/testing, but there is no explicit documentation tying this to safely testing against non-production data or separating staging from production. Missing for 10: explicit sandbox/staging environment separate from production data, evidence of data isolation guarantees, and confirmation that AI agents (Copilot cloud agent) operate in an isolated sandbox rather than live repos/production systems.

        • [claimed-docs] “Launch a full, cloud-based development environment in seconds.”
        • [claimed-docs] “Copilot can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and c…”
        • [claimed-docs] “Copilot cloud agent can: * Research a repository * Create implementation plans * Fix bugs * Implement incremental new features * …”
        proof ↗⚑ flag
        Bitbucketnone0/10

        No evidence describes a sandbox/staging environment or test-data isolation feature for AI-native testing in Bitbucket; evidence covers CI/CD, code review, permissions, and unrelated community complaints. Missing for 10: any mention of sandbox environments, ephemeral test environments, or production-data isolation for AI workflows.

          ⚑ flag

        • ai-native userRely on versioned APIs with a documented deprecation policy

          weight 2 · round drawn
          GitHubnone0/10

          The evidence pack documents GitHub's REST and GraphQL APIs and fine-grained token permissions, but contains no mention of API versioning schemes or any documented deprecation policy/timeline for those APIs. Missing for 10: explicit API version headers/dates, a published deprecation schedule, and changelog/sunset notices.

          • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
          • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
          • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
          proof ↗⚑ flag
          Bitbucketnone0/10

          No evidence of a versioned API or documented deprecation policy; probes for OpenAPI/docs endpoints returned 404s and no mention of API versioning or deprecation exists in the evidence pack.

          • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
          • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
          proof ↗⚑ flag

        Automation depth — how much of the product can run unattendedAutomation depth

        How much of the product can run unattended

        1. ai-native userPerform bulk operations across many items at once

          weight 2 · round to GitHub
          GitHubpartialprobed5/10

          GitHub exposes REST and GraphQL APIs plus a scriptable CLI that AI-native users could combine to perform bulk operations (e.g., scripting across many issues/repos), and GitHub Actions can automate repeated workflows. However, there is no first-party documented 'bulk operations' feature or Copilot/agent capability explicitly designed for acting across many items at once—only the underlying API/CLI primitives are shown. Missing for 10: explicit bulk-edit/bulk-action documentation, an AI-agent example of operating across many items, and independent evidence of this being used at scale.

          • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
          • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
          • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
          • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line.”
          • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
          • [probe] “official CLI documented at https://cli.github.com/”
          proof ↗⚑ flag
          Bitbucketnone0/10

          No evidence describes bulk operations across many items (e.g., batch PR merges, bulk repo/branch management, mass API operations) for AI-native or automated workflows; docs focus on single-PR review, CI/CD pipelines, and policy enforcement rather than bulk/batch actions.

            ⚑ flag

          • ai-native userDefine rules that trigger actions automatically on events

            weight 3 · round to GitHub
            GitHubfullclaimed7/10

            GitHub Actions ('Automate, customize, and execute your software development workflows right in your repository') is exactly the mechanism for defining event-triggered automation rules (e.g., on push, PR, issue, schedule), which is a first-party, mainstream GitHub capability. Missing for 10: detailed docs snippets showing the actual trigger/event syntax (on: push, on: issues, etc.) and independent hands-on corroboration of automation reliability/depth.

            • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
            proof ↗⚑ flag
            Bitbucketpartialclaimed6/10

            Bitbucket supports event-driven automation via Pipelines (triggered on push/PR/tag events), merge checks/branch policies, and Jira issue auto-updates on commit events, which cover core event→action rule triggering. However there's no dedicated declarative 'rules engine' (like Jira Automation) for defining custom conditional triggers beyond CI/CD pipeline YAML and merge-check policies. Missing for 10: a first-class no-code rules/automation builder for arbitrary event-condition-action logic, and independent hands-on validation of rule reliability.

            • [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
            • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
            • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
            • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
            • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
            proof ↗⚑ flag

          • ai-native userSchedule recurring jobs or workflows

            weight 2 · round drawn
            GitHubnone0/10

            The evidence describes GitHub Actions only in general terms ('automate...workflows') without any explicit mention of scheduled/cron-triggered or recurring job capability, so per the evidence-only rule this mainstream capability cannot be credited as documented here.

            • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
            proof ↗⚑ flag
            Bitbucketnone0/10

            The evidence describes CI/CD pipelines, AI-triggered workflows, and merge automation, but no citation mentions scheduling recurring jobs or cron-like automation. Missing for 10: any mention of scheduled/recurring pipeline triggers, cron syntax, or automated recurring task execution.

            • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
            • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
            • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
            proof ↗⚑ flag

          • ai-native userVersion, review, and roll back my automations

            weight 1 · round to GitHub
            GitHubpartialclaimed5/10

            GitHub Actions workflows live as code in the repository (github-docs-38), which implies they inherit git's native versioning and rollback via commits/PRs, but the evidence pack never explicitly documents PR-based review or revert workflows applied specifically to automations/workflow files. Missing for 10: explicit documentation of reviewing workflow-file changes via pull requests, rolling back a workflow to a prior version, and any audit/history UI specific to Actions.

            • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
            • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
            proof ↗⚑ flag
            Bitbucketpartialclaimed4/10

            Bitbucket Pipelines configs live in the same git repo, so pull-request review (docs-7, docs-11) and change-management enforcement (docs-6) apply to pipeline/automation changes, and AI-powered pipeline workflows are documented (docs-4, docs-8, docs-10). However, no evidence explicitly confirms automation-specific versioning history, dedicated review flows for automation scripts, or a rollback mechanism for automations. Missing for 10: explicit documentation of automation version history/diffing, dedicated review workflow for automation changes, and an explicit rollback/undo feature for pipeline or Rovo-triggered automations.

            • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
            • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
            • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
            • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
            • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
            proof ↗⚑ flag

          Ci cd — continuous integration and delivery — pipelines, runners, cachingCi cd

          Continuous integration and delivery — pipelines, runners, caching

          Deployment

          1. developerAutomate application deployments as part of my CI/CD pipeline

            weight 2 · round drawn
            GitHubfullclaimed7/10

            GitHub Actions is explicitly positioned for CI/CD automation ('Ship faster with secure, reliable CI/CD', 'Automate...software development workflows...with GitHub Actions'), and the Marketplace shows real deployment integrations (Render CI/CD, Shopify 'push to deploy', mobile CI/CD apps) that developers can wire into pipelines. Missing for 10: deeper first-party docs on deployment-specific features (environments, approval gates, rollback) and independent hands-on confirmation of a deployment pipeline working end-to-end.

            • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
            • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
            • [claimed-docs] “Continuous integration and deploys with Render, the modern cloud for ambitious developers”
            • [claimed-docs] “Build themes and headless faster with Shopify for GitHub. Connect any repository, then push to deploy”
            • [claimed-docs] “Cloud-based continuous integration and delivery for Android, iOS, Flutter, React Native, Ionic and Unity projects”
            proof ↗⚑ flag
            Bitbucketfullclaimed7/10

            Bitbucket Pipelines is documented as a built-in CI/CD tool for automated workflows, with deployment environments, permissions, and centralized visibility across pipeline/deployment status, supporting deployment automation as part of CI/CD. Missing for 10: hands-on/independent evidence of deployment pipeline execution, detailed deployment-specific docs (e.g., deployment triggers, rollback), and no community corroboration of deployment automation specifically.

            • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
            • [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
            • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
            • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
            proof ↗⚑ flag

          2. devops-leadMap incidents to deployments and require change approval before releases

            weight 1 · round to Bitbucket
            GitHubnone0/10

            The evidence pack contains only generic CI/CD and Actions references (github-docs-11, github-docs-38) but nothing on deployment environments, required-reviewer approval gates, or incident-to-deployment traceability/mapping, which are the specific capabilities this story asks about. Missing for 10: environment protection rules/required approvals before deploy, incident tracking or linking incidents to specific deployments, any audit trail connecting rollbacks/incidents to release history.

            • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
            • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
            proof ↗⚑ flag
            Bitbucketfullclaimed8/10

            Bitbucket docs explicitly state that incidents can be mapped to deployments and automated change approval processes enabled via integration with Jira Service Management, directly matching the story, and this is reinforced by merge checks/CI-CD policy enforcement features. Missing for 10: independent/hands-on verification of the incident-deployment mapping workflow beyond vendor docs.

            • [claimed-docs] “Enable automated change approval processes and resolve incidents faster by mapping incidents to deployments with Bitbucket and Jira Service …”
            • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
            • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
            proof ↗⚑ flag

          Dev environments

          1. developerLaunch a ready-to-code cloud-based development environment in seconds

            weight 2 · round to GitHub
            GitHubpartialclaimed5/10

            GitHub's marketing page explicitly claims 'Launch a full, cloud-based development environment in seconds' (github-docs-3), directly matching the story, but this is a single thin marketing line with no elaboration on Codespaces features, setup workflow, or independent/hands-on corroboration in the evidence pack. Missing for 10: detailed docs on Codespaces setup/config, first-hand user reports confirming fast launch times, and any independent verification of the 'seconds' claim.

            • [claimed-docs] “Launch a full, cloud-based development environment in seconds.”
            proof ↗⚑ flag
            Bitbucketnone0/10

            No evidence of a cloud dev environment / instant workspace feature (like Codespaces or Gitpod) in Bitbucket's evidence pack; the docs focus on CI/CD pipelines, code review, and Jira integration but never mention a ready-to-code cloud IDE or ephemeral dev environment launch.

              ⚑ flag

            Pipeline authoring

            1. developerReuse community-built CI/CD actions or plugins in my pipelines

              weight 2 · round to GitHub
              GitHubfullclaimed8/10

              GitHub Actions supports pulling in reusable community actions, and the GitHub Marketplace explicitly lists third-party CI/CD apps/actions (Render, Bitrise, Appcircle, Shopify, etc.) that developers can plug into pipelines, backed by official docs on Actions and the Marketplace ecosystem. missing for 10: independent/hands-on developer testimony specifically about reusing marketplace CI/CD actions (evidence is vendor docs/marketplace listings only).

              • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
              • [claimed-docs] “Extend your stack with apps, actions, and AI models.”
              • [claimed-docs] “Tools from the community and partners to simplify tasks and automate processes”
              • [claimed-docs] “Build on your workflow with apps that integrate with GitHub”
              • [claimed-docs] “Continuous integration and deploys with Render, the modern cloud for ambitious developers”
              • [claimed-docs] “Cloud-based continuous integration and delivery for Android, iOS, Flutter, React Native, Ionic and Unity projects”
              • [claimed-docs] “Build themes and headless faster with Shopify for GitHub. Connect any repository, then push to deploy”
              proof ↗⚑ flag
              Bitbucketnone0/10

              The evidence pack describes Bitbucket Pipelines, security integrations like Snyk, and connections to on-prem CI tools, but never mentions a marketplace of community-built Pipes/actions or reusable third-party pipeline plugins that developers can drop into their pipelines.

                ⚑ flag

              • developerDefine CI/CD pipelines as code using a YAML syntax

                weight 3 · round to GitHub
                GitHubfullcommunity8/10

                GitHub Actions is documented as GitHub's native CI/CD system, explicitly described as letting developers 'automate, customize, and execute software development workflows right in your repository' and 'ship faster with secure, reliable CI/CD' — Actions workflows are the standard code-as-config CI/CD mechanism. Missing for 10: explicit documentation snippet showing YAML workflow syntax itself and independent hands-on confirmation of writing pipeline YAML.

                • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
                • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
                • [community] “Complaint that GitHub Actions outages seem to correlate with new feature releases, impacting the dev team and infra 'seemingly every week.'”
                • [community] “User credits GitLab for 'pushing the market forward on affordable collaborative development' and says their team moved to GitHub only after …”
                proof ↗⚑ flag
                Bitbucketpartialclaimed6/10

                Bitbucket Pipelines is documented as the built-in CI/CD tool supporting hosted/private runners and centralized pipeline visibility, which aligns with a pipelines-as-code model, but the evidence never explicitly states the YAML file syntax (e.g., bitbucket-pipelines.yml) developers use to define pipelines. Missing for 10: explicit mention of YAML config file/syntax, example pipeline definitions, and independent hands-on confirmation of the YAML authoring experience.

                • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
                • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
                • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                proof ↗⚑ flag

              Runners

              1. devops-leadRun CI/CD jobs on runners hosted by the platform without managing infrastructure

                weight 3 · round to Bitbucket
                GitHubpartialcommunity6/10

                GitHub Actions is documented as providing CI/CD 'right in your repository' (github-docs-38) and marketed as 'secure, reliable CI/CD' (github-docs-11), implying GitHub-hosted runners without customer-managed infrastructure, and GitHub also supports self-hosted runners as an alternative option (github-comm-20 notes org-level self-hosted runner gaps, implying hosted runners are the default). However, community evidence reports recurring GitHub Actions outages 'seemingly every week' correlating with feature releases (github-comm-18) and broader platform outage concerns (github-comm-1, github-comm-2), which undercut confidence in the 'without managing infrastructure' reliability promise even though the core hosted-runner capability itself is not disputed. Missing for 10: explicit documentation/specs of hosted runner types, concurrency limits, or setup steps, and independent hands-on confirmation of smooth, infrastructure-free operation rather than just marketing taglines and outage complaints.

                • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
                • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
                • [community] “Complaint that GitHub Actions outages seem to correlate with new feature releases, impacting the dev team and infra 'seemingly every week.'”
                • [community] “User notes GitHub still lacks self-hosted runners for organizations, which would make it a stronger alternative to GitLab for teams.”
                • [community] “Ghostty project is leaving GitHub; author kept a journal marking an 'X' next to every date a GitHub outage negatively impacted his ability t…”
                proof ↗⚑ flag
                Bitbucketfullclaimed8/10

                Docs explicitly state Bitbucket Pipelines provides hosted runners so teams can run CI/CD workflows 'no infrastructure needed', with centralized visibility across pipelines, and also offers private runners as an alternative. Missing for 10: independent/hands-on corroboration of hosted-runner reliability or scale, and no detail on hosted runner resource limits/pricing.

                • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
                • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
                proof ↗⚑ flag

              2. devops-leadGet centralized visibility into CI/CD workflow runs across the organization

                weight 2 · round to Bitbucket
                GitHubpartialclaimed3/10

                GitHub Actions is documented as the CI/CD engine ('Automate...workflows...with GitHub Actions' and 'Ship faster with secure, reliable CI/CD'), implying pipelines exist, but the evidence pack contains no mention of an organization-wide dashboard, insights page, or cross-repo workflow-run visibility feature that a devops-lead would use. Missing for 10: org-level Actions insights/usage dashboard, cross-repo run aggregation, audit/reporting APIs for workflow runs, and any independent corroboration of centralized visibility.

                • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
                • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
                proof ↗⚑ flag
                Bitbucketpartialclaimed6/10

                Docs claim centralized visibility into pipeline status, testing policies, and deployment environments across the org via Bitbucket Pipelines (hosted/private runners), with policy enforcement across teams and repos. However, this is vendor-only marketing copy with no independent/hands-on corroboration of an actual cross-org dashboard or reporting UI, and no detail on how granular or org-wide the visibility truly is. Missing for 10: independent verification of the centralized dashboard's usability/completeness, detail on cross-project rollups, and community evidence confirming it works at scale.

                • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
                • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
                proof ↗⚑ flag

              3. devops-leadRun CI/CD jobs on my own self-hosted or private runners

                weight 2 · round to Bitbucket
                GitHubnone0/10

                The evidence pack only shows generic GitHub Actions marketing copy (github-docs-38, github-docs-11) with no documentation of self-hosted or private runner configuration, and the one specific piece of evidence on this topic (github-comm-20) states that GitHub 'still lacks self-hosted runners for organizations,' i.e. contradicts the story rather than supporting it.

                • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
                • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
                • [community] “User notes GitHub still lacks self-hosted runners for organizations, which would make it a stronger alternative to GitLab for teams.”
                proof ↗⚑ flag
                Bitbucketfullclaimed7/10

                Bitbucket docs explicitly state you can run CI/CD workflows using 'hosted or private runners—or both,' with centralized visibility, directly matching the self-hosted/private runner story, and also supports connecting to on-prem CI/CD tools like Bamboo or Jenkins. Missing for 10: independent/hands-on corroboration of private runner setup or reliability, and detail on runner configuration/scaling.

                • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
                • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
                proof ↗⚑ flag

              Ecosystem integrations — the surrounding ecosystem — integrations, marketplaces, community packagesEcosystem integrations

              The surrounding ecosystem — integrations, marketplaces, community packages

              Chat notifications

              1. developerSync repository notifications and activity with chat tools

                weight 1 · round to GitHub
                GitHubpartialclaimed5/10

                GitHub Marketplace lists a Slack integration ('Connect your code without leaving Slack') enabling repo activity/notifications to sync with chat, and Atlassian integration also syncs dev activity, but the evidence pack lacks first-party GitHub docs detailing notification-sync configuration, scope, or independent hands-on confirmation of reliability. missing for 10: official GitHub docs on the Slack/Teams integration setup and notification types, independent user confirmation that sync works well in practice.

                • [claimed-docs] “Connect your code without leaving Slack”
                • [claimed-docs] “GitHub for Atlassian unifies data, automates workflows, and syncs development across GitHub, Jira, and your Atlassian apps”
                • [claimed-docs] “Build on your workflow with apps that integrate with GitHub”
                proof ↗⚑ flag
                Bitbucketnone0/10

                No evidence pack item mentions Slack/Teams/chat notification integrations or activity syncing with chat tools; all docs focus on Jira, CI/CD, security scanning, and AI features. Missing for 10: any mention of Slack/Teams integration, chat notification setup, or activity feed syncing to chat tools.

                  ⚑ flag

                External ci cd integration

                1. devops-leadConnect the platform to external CI/CD tools instead of using its native pipelines

                  weight 1 · round to Bitbucket
                  GitHubfullclaimed7/10

                  GitHub's own Marketplace lists third-party CI/CD integrations (Render, mobile CI/CD tools) that plug into GitHub repos as alternatives to native Actions pipelines, and GitHub explicitly markets an extensible apps/actions ecosystem. This confirms devops leads can wire in external CI/CD tools rather than relying solely on GitHub Actions. Missing for 10: deeper first-party docs on webhook/status-API integration patterns for custom CI/CD tools, and independent hands-on confirmation of using a non-Actions CI/CD pipeline end-to-end with GitHub.

                  • [claimed-docs] “Continuous integration and deploys with Render, the modern cloud for ambitious developers”
                  • [claimed-docs] “Cloud-based continuous integration and delivery for Android, iOS, Flutter, React Native, Ionic and Unity projects”
                  • [claimed-docs] “Extend your stack with apps, actions, and AI models.”
                  • [claimed-docs] “Build on your workflow with apps that integrate with GitHub”
                  • [claimed-docs] “Tools from the community and partners to simplify tasks and automate processes”
                  proof ↗⚑ flag
                  Bitbucketfullclaimed8/10

                  Bitbucket docs explicitly state you can use built-in Pipelines 'or connect Bitbucket Cloud to on-prem CI/CD tools like Bamboo or Jenkins,' directly confirming external CI/CD integration as an alternative to native pipelines. Missing for 10: independent/hands-on corroboration of setting up Jenkins/Bamboo integration and broader detail on other third-party CI/CD tool support beyond Bamboo/Jenkins.

                  • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
                  proof ↗⚑ flag

                Marketplace extensions

                1. developerExtend my stack with third-party apps, actions, and AI models from a marketplace

                  weight 2 · round to GitHub
                  GitHubfullclaimed9/10

                  GitHub Marketplace explicitly offers apps, actions, and AI models to extend the developer stack, with documented examples spanning CI/CD, deployment, project management, chat, and IDE integrations (github-docs-10, github-docs-22, github-docs-35, github-intdir-1..7), plus Copilot's multi-model support (github-docs-34, github-docs-43). missing for 10: independent hands-on review specifically validating marketplace app/action installation quality or breadth beyond vendor listings.

                  • [claimed-docs] “Extend your stack with apps, actions, and AI models.”
                  • [claimed-docs] “Build on your workflow with apps that integrate with GitHub”
                  • [claimed-docs] “Tools from the community and partners to simplify tasks and automate processes”
                  • [claimed-docs] “Continuous integration and deploys with Render, the modern cloud for ambitious developers”
                  • [claimed-docs] “Keep your Lovable project synced both ways”
                  • [claimed-docs] “Login to OpenCode through Github Copilot”
                  • [claimed-docs] “GitHub for Atlassian unifies data, automates workflows, and syncs development across GitHub, Jira, and your Atlassian apps”
                  • [claimed-docs] “Connect your code without leaving Slack”
                  • [claimed-docs] “Build themes and headless faster with Shopify for GitHub. Connect any repository, then push to deploy”
                  • [claimed-docs] “Cloud-based continuous integration and delivery for Android, iOS, Flutter, React Native, Ionic and Unity projects”
                  • [claimed-docs] “GitHub Copilot supports multiple AI models, each with different strengths. Some prioritize speed and cost-efficiency, while others are optim…”
                  • [claimed-docs] “Automatically select the best model for each task.”
                  proof ↗⚑ flag
                  Bitbucketpartialclaimed5/10

                  Evidence shows some third-party/AI extensibility — Snyk security scanning integration, ability to connect to on-prem CI/CD tools, and Rovo AI model access in terminal/IDE — but there's no explicit mention of an app marketplace, listing of third-party apps, or an ecosystem of installable actions comparable to a dedicated marketplace story. Missing for 10: explicit marketplace/app directory documentation, breadth of third-party app listings, and independent corroboration of marketplace usage.

                  • [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
                  • [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
                  • [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
                  • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
                  proof ↗⚑ flag

                Security tool integrations

                1. devops-leadInstall third-party security scanning integrations directly from a security tab

                  weight 1 · round to Bitbucket
                  GitHubpartialclaimed3/10

                  Evidence shows GitHub has a general Marketplace for third-party apps/integrations (github-docs-22, github-intdir-*) and native security features like secret scanning, push protection, and Copilot Autofix (github-docs-7, github-docs-14, github-docs-15), but no evidence specifically describes installing third-party security scanning tools directly from a repository's Security tab. Missing for 10: documentation of the Security tab's integration/install UI, examples of third-party scanners (e.g. Snyk, Semgrep) being installed via that tab, and any workflow showing SARIF-based third-party results surfacing there.

                  • [claimed-docs] “Build on your workflow with apps that integrate with GitHub”
                  • [claimed-docs] “Detect, prevent, and remediate leaked secrets across your organization.”
                  • [claimed-docs] “Leverage security campaigns and Copilot Autofix to reduce application vulnerabilities.”
                  • [claimed-docs] “GitHub push protection confirms and displays an active secret, and blocks the push.”
                  • [claimed-docs] “Continuous integration and deploys with Render, the modern cloud for ambitious developers”
                  • [claimed-docs] “Cloud-based continuous integration and delivery for Android, iOS, Flutter, React Native, Ionic and Unity projects”
                  proof ↗⚑ flag
                  Bitbucketfullclaimed8/10

                  Docs explicitly confirm running automated security scans via out-of-the-box Snyk integration installed directly from the Security tab, plus support for connecting other providers, matching the story closely. Missing for 10: independent/hands-on corroboration of the Security tab install flow and breadth of third-party scanner ecosystem beyond Snyk.

                  • [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
                  proof ↗⚑ flag

                Governance — stories about governance in this arenaGovernance

                Stories about governance in this arena

                Licensing cost management

                1. devops-leadMake a single annual commitment and flexibly allocate spend across seat-based and usage-based licensing

                  weight 1 · round drawn
                  GitHubnone0/10

                  The evidence pack contains no mention of annual commitments, seat-based vs usage-based licensing flexibility, or spend allocation/billing governance features; only a single note about paying extra for exhausted AI credits (individual usage-based billing), which does not address enterprise annual commitment or flexible seat/usage allocation.

                  • [claimed-docs] “If you exhaust your AI credits, you can pay extra to keep working.”
                  • [claimed-docs] “This plan includes limited access to a selection of Copilot features allowing you to try AI-powered coding assistance at no cost.”
                  proof ↗⚑ flag
                  Bitbucketnone0/10

                  No evidence in the pack addresses annual commitment pricing, unified spend pools, or flexible allocation across seat- and usage-based licensing; only per-user pricing anecdotes and product feature docs are present.

                    ⚑ flag

                  Onboarding

                  1. developerAccess built-in resources to learn the Git version control system

                    weight 1 · round drawn
                    GitHubnone0/10

                    The evidence pack covers GitHub CLI, SSH setup, Copilot, APIs, and marketplace integrations, but contains no citation of built-in resources for learning Git itself (e.g., Git tutorials, Git Handbook, GitHub Skills courses). While such a capability is plausible for a platform like GitHub, nothing in the evidence documents it.

                      ⚑ flag
                      Bitbucketnone0/10

                      No evidence pack items reference built-in Git tutorials, guides, or learning resources for the Git version control system itself; the docs focus on Jira integration, CI/CD, AI review, permissions, and security, not educational content about learning Git.

                        ⚑ flag

                      Policy enforcement

                      1. devops-leadRequire automated change approval workflows before code reaches production

                        weight 1 · round to Bitbucket
                        GitHubnone0/10

                        The evidence pack contains no mention of branch protection rules, required reviewers, CODEOWNERS enforcement, or deployment environment approval gates that would block code from reaching production without sign-off. Docs only reference Copilot-assigned code reviews and generic CI/CD messaging, neither of which describes a governance/approval-gating workflow.

                          ⚑ flag
                          Bitbucketfullclaimed7/10

                          Bitbucket docs explicitly describe merge checks, branch permissions, CI/CD policy enforcement, and an explicit 'automated change approval process' integration with Jira Service Management mapping incidents to deployments, directly matching the governance story. Missing for 10: independent/hands-on verification of approval gating in practice and more detail on multi-stage production approval workflows beyond marketing copy.

                          • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                          • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
                          • [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
                          • [claimed-docs] “Enable automated change approval processes and resolve incidents faster by mapping incidents to deployments with Bitbucket and Jira Service …”
                          proof ↗⚑ flag

                        • devops-leadEnforce coding standards and CI/CD policies across all teams and repositories

                          weight 2 · round drawn
                          GitHubpartialclaimed6/10

                          GitHub provides organization-wide governance levers referenced in the evidence — secret scanning/push protection across the org (github-docs-7, github-docs-15), configurable Copilot policies that apply everywhere Copilot is used (github-docs-53), fine-grained token permission controls (github-docs-18/19/21/42), and CI/CD via Actions (github-docs-11, github-docs-38) — which together let a devops-lead push standards and pipeline behavior broadly. However, the pack lacks explicit evidence of core enforcement mechanisms like org-wide branch protection rules, required status checks/reviews, rulesets, or CODEOWNERS enforcement across repos. Missing for 10: branch protection/rulesets enforcement, required status checks tied to CI/CD gating, CODEOWNERS/required-reviewer policy documentation, and independent confirmation that these policies are consistently enforced at scale.

                          • [claimed-docs] “Detect, prevent, and remediate leaked secrets across your organization.”
                          • [claimed-docs] “GitHub push protection confirms and displays an active secret, and blocks the push.”
                          • [claimed-docs] “you can configure settings for GitHub Copilot on GitHub. The settings apply wherever you use GitHub Copilot.”
                          • [claimed-docs] “Ship faster with secure, reliable CI/CD.”
                          • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
                          • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
                          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
                          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions.”
                          • [claimed-docs] “Permissions define what resources the token can access via the API.”
                          proof ↗⚑ flag
                          Bitbucketpartialcommunity6/10

                          First-party docs directly claim enforcement of coding standards, CI/CD policies, merge checks, and granular permissions across teams/repos (bitbucket-docs-6, -7, -8, -9), which is exactly the story asked for. However, independent community evidence shows a real gap: an admin reported no way to prevent team members from making repositories public in Bitbucket Enterprise Cloud, undercutting the 'control at scale' claim (bitbucket-comm-19). Missing for 10: independent corroboration that merge-check/CI policy enforcement actually works at scale, and resolution of the reported permission-control gap.

                          • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                          • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
                          • [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
                          • [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
                          • [community] “It appears that in bitbucket enterprise cloud, there is no way for an administrator to prevent members of my team from making repositories p…”
                          proof ↗⚑ flag

                        Openness — open source, data portability, and self-hosting storiesOpenness

                        Open source, data portability, and self-hosting stories

                        1. ai-native userDo everything through the API that I can do in the UI

                          weight 2 · round to GitHub
                          GitHubpartialprobed7/10

                          GitHub exposes a comprehensive REST API and GraphQL API, fine-grained token permissions, and an official CLI/SSH access that together let users perform most repository, issue, PR, and workflow actions programmatically (github-docs-40, github-docs-41, github-docs-18/19/21/42, github-docs-31/32/37, github-probe-4). However, the evidence never claims full 1:1 parity between every UI feature (e.g., some admin/org settings, Copilot UI toggles) and the API, so full equivalence is not documented. Missing for 10: explicit parity statement or audit showing every UI action has an API/CLI equivalent, and independent confirmation of no UI-only features.

                          • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
                          • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
                          • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
                          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
                          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions.”
                          • [claimed-docs] “Permissions define what resources the token can access via the API.”
                          • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
                          • [claimed-docs] “Enter `gh repo clone OWNER/REPO`. For example, `gh repo clone octo-org/octo-repo` clones the `octo-org/octo-repo`”
                          • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line.”
                          • [probe] “official CLI documented at https://cli.github.com/”
                          • [probe] “official MCP server documented at https://github.com/github/github-mcp-server”
                          proof ↗⚑ flag
                          Bitbucketnone0/10

                          No evidence describes Bitbucket's REST API coverage or parity with UI features; probes show missing OpenAPI/docs endpoints, and no documentation claims full API-UI parity.

                          • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
                          • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
                          • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
                          proof ↗⚑ flag

                        2. ai-native userExport all of my data in open formats and leave

                          weight 3 · round to GitHub
                          GitHubpartialcommunity5/10

                          GitHub documents git-native portability (clone/download-zip/fork) and REST/GraphQL APIs that let users pull out repository and account data in open formats, which supports leaving the platform with code intact (github-docs-50, github-docs-41, github-docs-40, github-docs-33). However there is no evidence of a comprehensive 'export all my data' feature (issues, PR history, wiki, settings) beyond code, and community commentary shows some users have actually left GitHub citing lock-in concerns without contradicting the export mechanics themselves (github-comm-1, github-comm-7). Missing for 10: dedicated full-account data export/GDPR-style export documentation, evidence of exporting non-code artifacts (issues/projects/discussions) in open formats, and independent confirmation that a full migration-out process works smoothly.

                          • [claimed-docs] “You can: Download a snapshot of a repository's files as a zip file to your own (local) computer. Clone a repository to your local computer u…”
                          • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
                          • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
                          • [claimed-docs] “you must generate a new SSH key to use for authentication... you can add the public key to your account on GitHub.com to enable authenticati…”
                          • [community] “Ghostty project is leaving GitHub; author kept a journal marking an 'X' next to every date a GitHub outage negatively impacted his ability t…”
                          • [community] “Critic argues GitHub was always proprietary and locks users in, and welcomes anyone moving off it: 'Fuck Github. Every single outage Microsl…”
                          proof ↗⚑ flag
                          Bitbucketnone0/10

                          No evidence of any data export/portability feature or open-format export capability for Bitbucket repos/issues; probes even show missing docs/API endpoints. Since git repos are inherently portable, this axis is fair for a code-hosting product, but nothing in the evidence pack confirms an explicit export-and-leave capability.

                          • [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
                          • [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
                          • [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
                          proof ↗⚑ flag

                        3. ai-native userSelf-host the core product

                          weight 3 · round to Bitbucket
                          GitHubnone0/10

                          GitHub.com is a proprietary hosted SaaS; there is no evidence of a self-hostable core product (GitHub Enterprise Server, which does exist, is not mentioned anywhere in the pack). Absence of evidence for this applicable capability yields 'none'.

                            ⚑ flag
                            Bitbucketpartialclaimed4/10

                            Evidence indicates Bitbucket Data Center/Server exists as a self-hosted deployment option (docs mention migrating code from 'Bitbucket Server or Data Center' to Cloud and trialing Cloud 'for the same user count as your Bitbucket Data Center license'), confirming self-hosting is possible, but no documentation describes setup, feature parity, or AI-native workflows for the self-hosted version. Missing for 10: dedicated self-host installation docs, feature parity details for Data Center, and any independent/hands-on confirmation of self-hosting the core product.

                            • [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
                            • [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
                            proof ↗⚑ flag

                          Privacy posture — data-handling and privacy storiesPrivacy posture

                          Data-handling and privacy stories

                          1. ai-native userChoose where my data is stored (region/residency)

                            weight 2 · round drawn
                            GitHubnone0/10

                            No evidence pack items mention data residency, regional storage options, or geographic data controls for GitHub or Copilot; all evidence covers unrelated Copilot features, CLI, MCP, and community sentiment.

                              ⚑ flag
                              Bitbucketnone0/10

                              No evidence pack items mention data residency, region selection, or geographic storage controls for Bitbucket; only generic security features like 2FA, IP allowlisting, and encryption are documented.

                                ⚑ flag

                              • ai-native userPrevent my data from being used to train AI models

                                weight 3 · round drawn
                                GitHubnone0/10

                                No evidence pack item addresses AI training data opt-out or data usage policies for Copilot; only settings/policy pages are mentioned without training-data specifics. Missing for 10: explicit documentation of an opt-out/setting to exclude user data from AI model training, third-party audits or community confirmation of enforcement.

                                  ⚑ flag
                                  Bitbucketnone0/10

                                  No evidence in the pack addresses data usage for AI model training, opt-out controls, or privacy commitments regarding Bitbucket/Rovo AI features; the pack only covers unrelated product features and community UX complaints.

                                    ⚑ flag

                                  • ai-native userControl data retention and deletion

                                    weight 2 · round drawn
                                    GitHubnone0/10

                                    No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for AI-native features (e.g., Copilot data usage/retention configuration). Only tangential permissions/token docs are present, which do not cover retention or deletion controls.

                                      ⚑ flag
                                      Bitbucketnone0/10

                                      No evidence in the pack addresses AI data retention/deletion controls specific to Bitbucket's AI features (Rovo, AI code reviewer); only generic security/permission features are mentioned, none about data retention or deletion policies for AI-processed data.

                                        ⚑ flag

                                      • ai-native userOpt out of telemetry and usage tracking

                                        weight 2 · round drawn
                                        GitHubnone0/10

                                        No evidence in the pack references telemetry opt-out, usage tracking controls, or privacy settings related to data collection; the closest items describe Copilot policy management (github-docs-53) without mentioning telemetry opt-out. This is a fair axis for a developer platform to address, but no supporting evidence exists.

                                          ⚑ flag
                                          Bitbucketnone0/10

                                          No evidence pack item addresses telemetry opt-out or usage-tracking controls for Bitbucket; all docs focus on unrelated CI/CD, AI code review, and permissions features.

                                            ⚑ flag

                                          Project planning — stories about project planning in this arenaProject planning

                                          Stories about project planning in this arena

                                          External pm sync

                                          1. developerManage external issue tracker items directly within the code hosting UI

                                            weight 1 · round to Bitbucket
                                            GitHubpartialclaimed5/10

                                            GitHub Marketplace lists 'GitHub for Atlassian' which syncs Jira issues with GitHub, letting developers see/manage Jira items alongside code, but this is a third-party app integration rather than a native GitHub feature, and only one such integration is evidenced. missing for 10: native in-UI external tracker management, first-party documentation of the Jira/GitHub sync UX, and independent confirmation the integration works well.

                                            • [claimed-docs] “GitHub for Atlassian unifies data, automates workflows, and syncs development across GitHub, Jira, and your Atlassian apps”
                                            • [claimed-docs] “Create issues and manage projects with tools that adapt to your code.”
                                            proof ↗⚑ flag
                                            Bitbucketfullclaimed8/10

                                            Bitbucket docs claim a built-in Jira UI for managing Jira issues directly within Bitbucket, plus opening Jira tickets from the PR screen and automatic status updates via commit issue keys, directly supporting external issue tracker management in the code hosting UI. Missing for 10: independent/hands-on corroboration of this specific Jira UI feature and detail on its scope/limitations.

                                            • [claimed-docs] “Reduce context-switching by managing your Jira issues in Bitbucket with the built-in Jira UI”
                                            • [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
                                            • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                            proof ↗⚑ flag

                                          2. developerAutomatically update linked issue tracker statuses by referencing issue keys in my commits

                                            weight 2 · round to Bitbucket
                                            GitHubpartialclaimed3/10

                                            The evidence pack does not document GitHub's native closing-keyword commit syntax, but it does show an official Atlassian integration that 'unifies data, automates workflows, and syncs development across GitHub, Jira' which implies some issue-status syncing capability from commits/PRs. This is thin, indirect evidence rather than a documented commit-keyword-to-status-update workflow. Missing for 10: explicit documentation of issue-key syntax in commit messages, confirmation that referencing keys auto-transitions ticket status in Jira or other trackers, and independent corroboration of this working end-to-end.

                                            • [claimed-docs] “GitHub for Atlassian unifies data, automates workflows, and syncs development across GitHub, Jira, and your Atlassian apps”
                                            • [claimed-docs] “Create issues and manage projects with tools that adapt to your code.”
                                            proof ↗⚑ flag
                                            Bitbucketfullclaimed7/10

                                            Bitbucket docs directly state that including a Jira issue key in commits automatically updates the linked Jira issue's status, and Bitbucket's Jira integration also allows opening/viewing tickets from PR screens. missing for 10: independent/hands-on corroboration of the auto-transition behavior and details on configuration (e.g., required smart commit syntax or workflow mapping).

                                            • [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
                                            • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                            proof ↗⚑ flag

                                          Issue tracking

                                          1. developerTrack requirements, features, and bugs using issues with milestones, time tracking, and dependencies

                                            weight 3 · round to Bitbucket
                                            GitHubpartialclaimed3/10

                                            Evidence only generically references GitHub Issues/Projects ('Organize everything from high-level roadmaps to everyday tasks', 'Create issues and manage projects with tools that adapt to your code') with no documentation of milestones, time tracking, or issue dependencies specifically. GitHub is known to support issues/milestones and dependency links via sub-issues, but no first-party doc in this pack confirms time tracking, which is not a native GitHub feature. Missing for 10: explicit docs on milestones, native time tracking, and dependency/sub-issue linking.

                                            • [claimed-docs] “Organize everything from high-level roadmaps to everyday tasks.”
                                            • [claimed-docs] “Create issues and manage projects with tools that adapt to your code.”
                                            proof ↗⚑ flag
                                            Bitbucketpartialclaimed4/10

                                            Bitbucket docs mention Jira issue integration (auto status updates on commit, built-in Jira UI in Bitbucket, opening Jira tickets from PRs) which covers basic issue tracking, but this relies entirely on a separate Jira product rather than native Bitbucket issue features, and there is no mention of milestones, time tracking, or dependency tracking anywhere in the evidence. missing for 10: native milestone support, time tracking, dependency linking, and evidence these work without requiring a separate Jira subscription.

                                            • [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
                                            • [claimed-docs] “Reduce context-switching by managing your Jira issues in Bitbucket with the built-in Jira UI”
                                            • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                            proof ↗⚑ flag

                                          2. developerManage projects and assign tasks from my mobile device

                                            weight 1 · round to GitHub
                                            GitHubfullclaimed8/10

                                            GitHub explicitly documents managing projects and assigning tasks to Copilot from a mobile device (github-docs-4), backed by GitHub Mobile's general capabilities (github-docs-54) and Projects features for organizing tasks (github-docs-8, github-docs-12). Missing for 10: independent hands-on corroboration of the mobile task-assignment workflow and more detail on mobile-specific project management UI limitations.

                                            • [claimed-docs] “Manage projects and assign tasks to Copilot, all from your mobile device.”
                                            • [claimed-docs] “GitHub Mobile gives you a way to do high-impact work on GitHub quickly and from anywhere.”
                                            • [claimed-docs] “Organize everything from high-level roadmaps to everyday tasks.”
                                            • [claimed-docs] “Create issues and manage projects with tools that adapt to your code.”
                                            proof ↗⚑ flag
                                            Bitbucketnone0/10

                                            No evidence describes a Bitbucket mobile app or mobile-optimized interface for managing projects or assigning tasks; docs focus on Jira integration, CI/CD, and code review, none of which mention mobile access.

                                              ⚑ flag

                                            • developerOrganize work from high-level roadmaps to everyday tasks using project boards

                                              weight 2 · round to GitHub
                                              GitHubfullclaimed7/10

                                              GitHub explicitly markets Projects as a way to 'Organize everything from high-level roadmaps to everyday tasks' and 'Create issues and manage projects with tools that adapt to your code,' directly matching the story, with mobile task assignment also mentioned. Missing for 10: deeper docs on project board views/customization (e.g., roadmap layouts, hierarchies) and independent/hands-on corroboration beyond marketing copy.

                                              • [claimed-docs] “Organize everything from high-level roadmaps to everyday tasks.”
                                              • [claimed-docs] “Create issues and manage projects with tools that adapt to your code.”
                                              • [claimed-docs] “Manage projects and assign tasks to Copilot, all from your mobile device.”
                                              proof ↗⚑ flag
                                              Bitbucketnone0/10

                                              No evidence in the pack mentions project boards, roadmaps, backlogs, or task/kanban planning views for Bitbucket itself; only Jira integration for issue status updates is mentioned, which is a separate product. This applicable planning axis has no supporting evidence.

                                                ⚑ flag

                                              Repos collaboration — working on repos together — pull requests, reviews, permissionsRepos collaboration

                                              Working on repos together — pull requests, reviews, permissions

                                              Code review

                                              1. ai-native userHave an AI reviewer analyze code changes and suggest fixes during review

                                                weight 2 · round to GitHub
                                                GitHubfullclaimed9/10

                                                GitHub Copilot directly supports AI code review: docs confirm Copilot 'can review your code and provide feedback' with 'suggested changes which you can apply with a couple of clicks' (github-docs-25), and PR-level review assignment via 'Assign initial reviews to Copilot for greater speed and quality' (github-docs-9), backed by Copilot Autofix for applying fixes (github-docs-5). Missing for 10: independent/hands-on community corroboration specifically of the review-and-suggest-fix workflow (community evidence covers general Copilot sentiment, not this specific feature).

                                                • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
                                                • [claimed-docs] “Assign initial reviews to Copilot for greater speed and quality.”
                                                • [claimed-docs] “Apply fixes in seconds. Spend less time debugging and more time building features with Copilot Autofix.”
                                                • [claimed-docs] “It suggests code as you type, answers questions about a codebase, reviews your changes, and works on tasks you assign it.”
                                                proof ↗⚑ flag
                                                Bitbucketpartialclaimed6/10

                                                Bitbucket's own docs explicitly claim an AI code reviewer that reviews changes and suggests fixes (bitbucket-docs-3), directly matching the story, and code review features are documented alongside it (bitbucket-docs-11). However, there is no independent/hands-on evidence corroborating this AI reviewer's real-world behavior or quality, and no detail on how suggestions are surfaced during PR review. missing for 10: independent/hands-on verification of the AI reviewer's accuracy and workflow, detailed documentation of the suggestion/fix mechanism.

                                                • [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
                                                • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                                proof ↗⚑ flag

                                              2. ai-native userAssign the initial code review of a pull request to an AI reviewer for faster turnaround

                                                weight 2 · round to GitHub
                                                GitHubfullclaimed9/10

                                                GitHub directly documents assigning initial PR reviews to Copilot ('Assign initial reviews to Copilot for greater speed and quality') and Copilot's code review capability with suggested changes ('GitHub Copilot can review your code and provide feedback... suggested changes'), matching the story precisely. Missing for 10: independent/hands-on evidence quantifying turnaround-speed improvement from AI-assigned reviews.

                                                • [claimed-docs] “Assign initial reviews to Copilot for greater speed and quality.”
                                                • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
                                                proof ↗⚑ flag
                                                Bitbucketpartialclaimed5/10

                                                Bitbucket docs claim an AI code reviewer that reviews all code changes and suggests fixes to speed merges, which addresses the core idea of AI-driven review turnaround, but there is no evidence describing an explicit 'assign as reviewer on a PR' workflow, configurability, or independent/hands-on confirmation of this feature working. missing for 10: evidence of assigning AI as a designated PR reviewer, setup/configuration details, and independent corroboration of real-world use.

                                                • [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
                                                • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                                proof ↗⚑ flag

                                              3. developerReview code changes online and respond to inline review comments

                                                weight 3 · round to Bitbucket
                                                GitHubnone0/10

                                                The evidence pack contains no documentation of GitHub's native pull-request review interface, inline comments, or developer-to-developer review threads; the closest match (github-docs-25) describes Copilot providing automated review feedback, not a human reviewing changes online and responding to another developer's inline comments. Missing for 10: any doc on PR diff view, inline comment threads, review approval/request-changes flow, or reply-to-comment functionality.

                                                  ⚑ flag
                                                  Bitbucketpartialclaimed6/10

                                                  Bitbucket's docs claim comprehensive PR code review features including reviewing diffs and commenting from the PR screen (bitbucket-docs-11), which implies inline review comments are supported, but no evidence explicitly confirms responding/threading on inline comments, and community feedback focuses on unrelated UI/browsing complaints rather than confirming this specific workflow. missing for 10: explicit documentation or hands-on evidence of inline comment threads/replies, independent corroboration of the review-comment workflow.

                                                  • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                                  proof ↗⚑ flag

                                                • developerReview large diffs and view third-party code quality reports directly in the review screen

                                                  weight 2 · round to Bitbucket
                                                  GitHubnone0/10

                                                  The evidence pack shows GitHub Copilot code review (github-docs-25), CI/CD via Actions (github-docs-38), and a marketplace of third-party integrations (github-intdir-1, github-intdir-7), but nothing explicitly describes large-diff handling in the PR review screen or third-party code-quality/coverage reports rendered inline as review annotations. missing for 10: documentation of large-diff review UX (e.g. diff pagination, file-by-file review tools), evidence of third-party check results (e.g. code coverage, linting, SAST) surfaced directly in the Files Changed/review screen via the Checks API.

                                                  • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
                                                  • [claimed-docs] “Automate, customize, and execute your software development workflows right in your repository with GitHub Actions.”
                                                  • [claimed-docs] “Continuous integration and deploys with Render, the modern cloud for ambitious developers”
                                                  • [claimed-docs] “Cloud-based continuous integration and delivery for Android, iOS, Flutter, React Native, Ionic and Unity projects”
                                                  proof ↗⚑ flag
                                                  Bitbucketfullclaimed8/10

                                                  Bitbucket docs explicitly state the product lets developers 'Review large diffs with ease, view third-party code reports, and open Jira tickets right from the PR screen,' directly matching the story. Missing for 10: independent/hands-on corroboration of this specific feature (community evidence discusses other UI aspects but not this capability).

                                                  • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                                  proof ↗⚑ flag

                                                • devops-leadEnforce standardized, customizable merge checks before code can be merged

                                                  weight 2 · round to Bitbucket
                                                  GitHubnone0/10

                                                  The evidence pack contains no mention of branch protection rules, required status checks, required reviews, or CODEOWNERS enforcement mechanisms that would let a devops-lead gate merges. Only generic CI/CD (github-docs-11, github-docs-38) and Copilot code review (github-docs-25) items appear, none of which describe enforceable, customizable merge gating.

                                                    ⚑ flag
                                                    Bitbucketfullclaimed8/10

                                                    Bitbucket docs explicitly state support for 'standardized, customizable merge checks' to enforce code quality, compliance, and CI/CD policies across teams and repos, backed by branch-level permission controls. Missing for 10: independent/hands-on corroboration of merge-check configuration in practice and detail on granularity of check types beyond marketing copy.

                                                    • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
                                                    • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                                                    • [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
                                                    proof ↗⚑ flag

                                                  Package registry

                                                  1. open-source-maintainerPublish and consume software packages in multiple package formats from the same platform

                                                    weight 2 · round drawn
                                                    GitHubnone0/10

                                                    The evidence pack contains no mention of GitHub Packages, container/npm/Maven/NuGet/RubyGems registries, or any multi-format package publishing/consumption capability — all citations focus on Copilot, Actions, CLI, MCP, and community sentiment. Since this is an applicable axis for a repo-hosting platform but no supporting evidence exists in the pack, it must be scored as 'none'.

                                                      ⚑ flag
                                                      Bitbucketnone0/10

                                                      No evidence in the pack mentions a package registry or multi-format package management capability (e.g., npm, Maven, Docker, PyPI) in Bitbucket; docs only reference container image/tag permissions in passing without describing a package publishing feature. Missing for 10: any documentation of a package registry, supported package formats, or publish/consume workflows.

                                                        ⚑ flag

                                                      Repo management

                                                      1. devops-leadControl granular access permissions at the workspace, project, repository, and branch level

                                                        weight 2 · round to Bitbucket
                                                        GitHubpartialclaimed4/10

                                                        Evidence only covers fine-grained personal access token permissions (API scoping) rather than GitHub's actual RBAC system for organizations/teams, repository roles, or branch protection rules that would satisfy a devops-lead's granular access control needs. Missing for 10: branch protection rules, team/organization-level repository permission management, and workspace/project-level access control documentation.

                                                        • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
                                                        • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
                                                        • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions.”
                                                        • [claimed-docs] “Permissions define what resources the token can access via the API.”
                                                        proof ↗⚑ flag
                                                        Bitbucketfullcommunity8/10

                                                        First-party docs explicitly state control over permissions at workspace, project, repo, and granular branch/environment/package levels (bitbucket-docs-9), directly matching the story, and is reinforced by broader policy/compliance enforcement claims (bitbucket-docs-6, bitbucket-docs-7). Missing for 10: independent hands-on corroboration of granular branch-level permission enforcement, and one community note (bitbucket-comm-19) suggests admins lack full control over repo visibility, indicating some gaps in enterprise-wide permission enforcement.

                                                        • [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
                                                        • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                                                        • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
                                                        • [community] “It appears that in bitbucket enterprise cloud, there is no way for an administrator to prevent members of my team from making repositories p…”
                                                        proof ↗⚑ flag

                                                      2. developerSearch across repositories to find code, files, and commits

                                                        weight 2 · round to GitHub
                                                        GitHubdisputedcontradicted3/10

                                                        GitHub's platform docs point to APIs (REST/GraphQL) for retrieving and querying repository data, which vendor-side implies broad search/query capability across repos, but a first-hand community report explicitly states GitHub's code search is 'terribly bad'—so poor that cloning and using grep is more effective—directly contradicting the polished vendor narrative. missing for 10: no dedicated vendor documentation on the actual code/commit/file search UI or its indexing depth, no independent corroboration of search quality beyond the negative report, and no evidence addressing recent search improvements.

                                                        • [claimed-docs] “The GitHub GraphQL API offers more precise and flexible queries than the GitHub REST API.”
                                                        • [claimed-docs] “Create integrations, retrieve data, and automate your workflows with the GitHub REST API.”
                                                        • [community] “Complaint that GitHub's code search is 'terribly bad'—so poor that it's more efficient to clone a repo and use plain grep instead.”
                                                        proof ↗⚑ flag
                                                        Bitbucketnone0/10

                                                        No vendor documentation in the evidence pack describes a code/commit search feature, and community reports explicitly state Bitbucket lacks a search feature ('there isn't even a search feature, let alone browse capability' and 'no search feature by language'), so there is no evidence the story is delivered.

                                                        • [community] “So how do I browse projects hosted on BitBucket? No search feature by language, no Explore feature like GitHub - can't test drive before sig…”
                                                        • [community] “I love bitbucket but I would like to be able to create clusters of related projects by language/tool. Right now there isn't even a search fe…”
                                                        proof ↗⚑ flag

                                                      3. developerCreate and manage Git repositories and browse their commit history

                                                        weight 3 · round to GitHub
                                                        GitHubfullclaimed7/10

                                                        Evidence confirms core repo management: cloning via GitHub CLI (`gh repo clone`), SSH-based git authentication for push/pull, and downloading/cloning/forking repositories are all documented first-party GitHub capabilities. However, no citation explicitly addresses browsing commit history UI/API features. Missing for 10: explicit documentation of commit history browsing (e.g., commit log view, blame, diff comparison) and independent hands-on corroboration of repo creation/management workflow.

                                                        • [claimed-docs] “Enter `gh repo clone OWNER/REPO`. For example, `gh repo clone octo-org/octo-repo` clones the `octo-org/octo-repo`”
                                                        • [claimed-docs] “You can: Download a snapshot of a repository's files as a zip file to your own (local) computer. Clone a repository to your local computer u…”
                                                        • [claimed-docs] “you must generate a new SSH key to use for authentication... you can add the public key to your account on GitHub.com to enable authenticati…”
                                                        • [claimed-docs] “You can access and write data in repositories on GitHub using SSH (Secure Shell Protocol).”
                                                        • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
                                                        • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line.”
                                                        proof ↗⚑ flag
                                                        Bitbucketfullcommunity6/10

                                                        Bitbucket is fundamentally a Git hosting platform, and community evidence confirms core repo hosting and commit-history browsing (praised commits view with graph, per-repo deploy keys, Mercurial repo hosting) even though some users criticize the web browsing UX and lack of a project explore/search feature. Missing for 10: first-party docs explicitly describing repo creation/management workflow, and resolution of complaints about slow/painful source browsing and missing cross-project browse/search.

                                                        • [community] “The redesigned commits view is 100 times better than Github's ever was - so much more info, and even a graph like in gitx.”
                                                        • [community] “As a daily Bitbucket user, browsing source code via web is painful and slow compared to Github's slicker UI with tree slider navigation.”
                                                        • [community] “So how do I browse projects hosted on BitBucket? No search feature by language, no Explore feature like GitHub - can't test drive before sig…”
                                                        • [community] “I love bitbucket but I would like to be able to create clusters of related projects by language/tool. Right now there isn't even a search fe…”
                                                        • [community] “Bitbucket's deploy key is read-only and can be attached to multiple repos, unlike Github's which is read-write and single-repo only - a much…”
                                                        • [community] “This is disappointing. Bitbucket is the premier place to host free private mercurial repos - there is literally not a single other place for…”
                                                        proof ↗⚑ flag

                                                      4. developerPropose, discuss, and merge code changes using a pull or merge request workflow

                                                        weight 3 · round to Bitbucket
                                                        GitHubfullclaimed6/10

                                                        Evidence confirms the pull-request workflow exists and is central to GitHub's Copilot-assisted development flow (agents 'create a pull request when you're ready', 'resolve merge conflicts', and Copilot can 'review your code and provide feedback' with suggested changes), which implies the underlying PR creation/discussion/merge mechanics. However, the pack lacks direct documentation of the core native PR UI itself (opening a PR, review comment threads, approve/merge buttons, conflict resolution UI) independent of Copilot. Missing for 10: first-party docs on PR creation/review UI, merge button and required-review settings, and independent/hands-on confirmation of the review-and-merge process.

                                                        • [claimed-docs] “Copilot can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and c…”
                                                        • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
                                                        • [claimed-docs] “Copilot cloud agent can: * Research a repository * Create implementation plans * Fix bugs * Implement incremental new features * …”
                                                        proof ↗⚑ flag
                                                        Bitbucketfullclaimed7/10

                                                        Bitbucket docs confirm comprehensive PR/code review features (opening PRs, reviewing diffs, merge checks, opening Jira tickets from PR screen) which directly support the propose/discuss/merge workflow. missing for 10: independent hands-on corroboration of the actual PR discussion/merge UX (community evidence focuses on repo browsing, pricing, and UI gripes rather than PR workflow specifics), and no detail on review comment threading or approval mechanics.

                                                        • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                                        • [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
                                                        • [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
                                                        proof ↗⚑ flag

                                                      Security — security posture and hardening storiesSecurity

                                                      Security posture and hardening stories

                                                      Access security

                                                      1. devops-leadRestrict repository access to specific IP address ranges

                                                        weight 2 · round to Bitbucket
                                                        GitHubnone0/10

                                                        No evidence in the pack mentions IP allow-listing or restricting repository/organization access by IP address range; GitHub Enterprise Cloud does offer this feature in reality, but nothing in the provided evidence documents it, so it must be marked none.

                                                          ⚑ flag
                                                          Bitbucketfullclaimed7/10

                                                          Bitbucket docs explicitly state IP allowlisting is a security feature to restrict code access to authorized users, directly matching the story. Missing for 10: detailed documentation on granularity (per-repo vs workspace-wide IP ranges), independent/hands-on confirmation, and enterprise-tier limitations.

                                                          • [claimed-docs] “2FA and IP allowlisting keep your code accessible only by authorized users. All code is encrypted in transit and at rest.”
                                                          proof ↗⚑ flag

                                                        • developerGenerate and manage personal access tokens for authenticating to the platform

                                                          weight 2 · round to GitHub
                                                          GitHubfullclaimed7/10

                                                          GitHub's docs describe fine-grained personal access tokens, including granting permissions and per-endpoint permission requirements via the X-Accepted-GitHub-Permissions header, confirming first-party support for creating and managing PATs for API authentication. missing for 10: no evidence on the full token lifecycle (e.g., expiration settings, revocation, token audit log) or classic PAT management UI, and no independent/hands-on corroboration of the token management workflow.

                                                          • [claimed-docs] “you will receive the `X-Accepted-GitHub-Permissions` header in the REST API response. The header will tell you what permissions are required…”
                                                          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the token can acc…”
                                                          • [claimed-docs] “When you create a fine-grained personal access token, you grant it a set of permissions.”
                                                          • [claimed-docs] “Permissions define what resources the token can access via the API.”
                                                          proof ↗⚑ flag
                                                          Bitbucketnone0/10

                                                          No evidence pack items mention personal access tokens or app passwords for authentication; only 2FA and IP allowlisting are cited, which do not address PAT generation/management. Missing for 10: any documentation or mention of personal access tokens, app passwords, or token scopes/lifecycle management.

                                                            ⚑ flag

                                                          • developerSet up SSH keys to authenticate and connect securely to the platform

                                                            weight 2 · round to GitHub
                                                            GitHubfullclaimed9/10

                                                            GitHub's official docs directly cover SSH key generation and adding it to the ssh-agent for authenticating Git operations over SSH, plus confirm SSH is a supported method to access/write repository data. missing for 10: no independent/hands-on corroboration of the SSH setup flow beyond first-party docs.

                                                            • [claimed-docs] “you must generate a new SSH key to use for authentication... you can add the public key to your account on GitHub.com to enable authenticati…”
                                                            • [claimed-docs] “You can access and write data in repositories on GitHub using SSH (Secure Shell Protocol).”
                                                            • [claimed-docs] “After you've checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.”
                                                            proof ↗⚑ flag
                                                            Bitbucketnone0/10

                                                            The evidence pack contains no first-party documentation describing SSH key setup or authentication for Bitbucket; the only relevant reference is a community complaint (bitbucket-comm-4) describing repeated authentication failures despite adding an SSH key, which does not establish that the feature works as expected. Without any vendor documentation or successful hands-on confirmation, there is no evidence the capability is delivered.

                                                            • [community] “I have to authenticate every time I push to the repo despite adding my SSH key; can't find equivalent to github.user/github.token config for…”
                                                            proof ↗⚑ flag

                                                          • developerSecure my account with two-factor authentication

                                                            weight 3 · round to Bitbucket
                                                            GitHubnone0/10

                                                            The evidence pack covers account creation, social login, SSH keys, and fine-grained PAT permissions, but contains no documentation or mention of two-factor authentication setup or enforcement for developer accounts. Without direct evidence for this specific security capability, it cannot be credited despite GitHub being widely known to offer 2FA.

                                                              ⚑ flag
                                                              Bitbucketfullclaimed7/10

                                                              Bitbucket docs explicitly state '2FA and IP allowlisting keep your code accessible only by authorized users,' confirming native two-factor authentication support for account security. Missing for 10: no independent/hands-on corroboration of the 2FA setup flow or details on supported methods (e.g., TOTP, SMS, hardware keys).

                                                              • [claimed-docs] “2FA and IP allowlisting keep your code accessible only by authorized users. All code is encrypted in transit and at rest.”
                                                              proof ↗⚑ flag

                                                            Vulnerability scanning

                                                            1. ai-native userHave AI automatically generate and apply fixes for detected security vulnerabilities

                                                              weight 2 · round to GitHub
                                                              GitHubfullclaimed8/10

                                                              GitHub Copilot Autofix directly targets this story: it auto-generates fixes for code-scanning-detected vulnerabilities ('Apply fixes in seconds... Copilot Autofix'), is used in 'security campaigns' to reduce vulnerabilities, and Dependabot updates vulnerable dependencies with supported fixes. Secret scanning/push protection covers detection and blocking of another vulnerability class. Missing for 10: independent/hands-on validation of Autofix accuracy and no detail on how automatically fixes are applied without human review.

                                                              • [claimed-docs] “Apply fixes in seconds. Spend less time debugging and more time building features with Copilot Autofix.”
                                                              • [claimed-docs] “Update vulnerable dependencies with supported fixes for breaking changes.”
                                                              • [claimed-docs] “Leverage security campaigns and Copilot Autofix to reduce application vulnerabilities.”
                                                              • [claimed-docs] “Detect, prevent, and remediate leaked secrets across your organization.”
                                                              • [claimed-docs] “GitHub push protection confirms and displays an active secret, and blocks the push.”
                                                              proof ↗⚑ flag
                                                              Bitbucketpartialclaimed4/10

                                                              Bitbucket integrates Snyk for automatic security scanning and has an AI code reviewer that 'suggests fixes' for code changes, plus AI-powered pipeline workflows that can automate fixes for some issues, but there is no evidence of AI automatically generating and applying patches specifically for detected security vulnerabilities. Missing for 10: explicit documentation of AI auto-remediation tied to Snyk/security scan findings, evidence of automatic PR creation/application of security fixes, and independent confirmation this works hands-on.

                                                              • [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
                                                              • [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
                                                              • [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
                                                              proof ↗⚑ flag

                                                            2. developerAutomatically receive pull requests that update vulnerable dependencies

                                                              weight 3 · round to GitHub
                                                              GitHubpartialclaimed5/10

                                                              github-docs-6 ("Update vulnerable dependencies with supported fixes for breaking changes") and github-docs-14 (security campaigns/Copilot Autofix to reduce vulnerabilities) point to GitHub's Dependabot-style automated dependency update capability, which is a well-known GitHub feature, but the evidence pack only contains thin marketing bullets rather than detailed first-party docs describing the automatic PR workflow. Missing for 10: dedicated Dependabot documentation describing PR creation triggers/config, and independent/hands-on corroboration that PRs are actually opened automatically.

                                                              • [claimed-docs] “Update vulnerable dependencies with supported fixes for breaking changes.”
                                                              • [claimed-docs] “Leverage security campaigns and Copilot Autofix to reduce application vulnerabilities.”
                                                              • [claimed-docs] “Apply fixes in seconds. Spend less time debugging and more time building features with Copilot Autofix.”
                                                              proof ↗⚑ flag
                                                              Bitbucketnone0/10

                                                              Evidence only shows Bitbucket offers security scanning via a Snyk integration (bitbucket-docs-12), but there is no mention of automatically generated pull requests to update vulnerable dependencies (a Dependabot-like feature). Missing for full credit: any documentation of automated dependency-update PR creation, PR scheduling/frequency settings, or dependency graph triggers.

                                                              • [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
                                                              proof ↗⚑ flag

                                                            3. devops-leadConsolidate static analysis, dependency, secret, and dynamic security scanning into one platform

                                                              weight 3 · round to GitHub
                                                              GitHubpartialclaimed6/10

                                                              Evidence shows GitHub bundles secret scanning/push protection (github-docs-7, github-docs-15), dependency vulnerability fixes (github-docs-6), and Copilot Autofix tied to security campaigns (github-docs-5, github-docs-14), which together imply static/code scanning plus dependency and secret scanning in one platform. However, there is no evidence of dynamic application security testing (DAST) being part of this consolidated offering. Missing for 10: explicit dynamic/DAST scanning capability, and independent/hands-on validation that all four scan types are unified in one dashboard.

                                                              • [claimed-docs] “Apply fixes in seconds. Spend less time debugging and more time building features with Copilot Autofix.”
                                                              • [claimed-docs] “Update vulnerable dependencies with supported fixes for breaking changes.”
                                                              • [claimed-docs] “Detect, prevent, and remediate leaked secrets across your organization.”
                                                              • [claimed-docs] “Leverage security campaigns and Copilot Autofix to reduce application vulnerabilities.”
                                                              • [claimed-docs] “GitHub push protection confirms and displays an active secret, and blocks the push.”
                                                              proof ↗⚑ flag
                                                              Bitbucketpartialclaimed4/10

                                                              Bitbucket documents an out-of-the-box Snyk integration for automatic security scans and mentions viewing third-party code reports in PRs, but this is a single third-party integration rather than a native unified platform combining static analysis, dependency, secret, and dynamic scanning. Missing for 10: native SAST/secret/DAST scanning tools, evidence of a single consolidated security dashboard, and independent confirmation the integration covers all four scan types.

                                                              • [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
                                                              • [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
                                                              proof ↗⚑ flag

                                                            4. devops-leadDetect and remediate leaked secrets across the organization's repositories

                                                              weight 2 · round to GitHub
                                                              GitHubfullclaimed8/10

                                                              GitHub explicitly advertises secret scanning to 'detect, prevent, and remediate leaked secrets across your organization' and push protection that blocks pushes containing active secrets, directly matching the devops-lead story. missing for 10: independent/hands-on corroboration of remediation workflow at org scale and detail on remediation tooling beyond blocking.

                                                              • [claimed-docs] “Detect, prevent, and remediate leaked secrets across your organization.”
                                                              • [claimed-docs] “GitHub push protection confirms and displays an active secret, and blocks the push.”
                                                              proof ↗⚑ flag
                                                              Bitbucketnone0/10

                                                              The evidence only mentions generic security scanning via Snyk integration and general permission/2FA controls, with no specific mention of secret detection, leaked credential scanning, or organization-wide remediation workflows. Missing for 10: any documentation of secret-scanning capability, push-protection, or remediation workflow for leaked credentials.

                                                              • [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
                                                              • [claimed-docs] “2FA and IP allowlisting keep your code accessible only by authorized users. All code is encrypted in transit and at rest.”
                                                              proof ↗⚑ flag

                                                            Self hosting — running it yourself — self-hosted servers, open-source clientsSelf hosting

                                                            Running it yourself — self-hosted servers, open-source clients

                                                            Deployment options

                                                            1. devops-leadRun my self-hosted instance on my choice of operating system and architecture, including containers

                                                              weight 2 · round drawn
                                                              GitHubnone0/10

                                                              The evidence pack contains no mention of GitHub Enterprise Server, self-hosted deployment options, supported operating systems/architectures, or container-based installation — all evidence describes GitHub.com as a cloud SaaS plus Copilot/CLI/API features. Self-hosting is a plausible axis for a dev platform like GitHub, but nothing in the pack substantiates it.

                                                                ⚑ flag
                                                                Bitbucketnone0/10

                                                                Evidence confirms a self-hosted Bitbucket Data Center product exists (migration tooling, DC license trials) but contains no documentation of supported operating systems, CPU architectures, or containerized/Docker deployment options.

                                                                • [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
                                                                • [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
                                                                proof ↗⚑ flag

                                                              • devops-leadScale my self-hosted installation using reference architectures supporting tens of thousands of users

                                                                weight 2 · round drawn
                                                                GitHubnone0/10

                                                                No evidence pack items discuss GitHub Enterprise Server self-hosting, reference architectures, or scaling guidance for tens of thousands of users; all citations concern Copilot, APIs, CLI, and community sentiment unrelated to self-hosted infrastructure scaling.

                                                                  ⚑ flag
                                                                  Bitbucketnone0/10

                                                                  No evidence of Bitbucket Data Center reference architectures, scaling benchmarks, or documentation for supporting tens of thousands of users; evidence only covers Cloud migration and generic feature descriptions.

                                                                    ⚑ flag

                                                                  • devops-leadUse migration tooling to move my code and users from another platform or from self-hosted to cloud

                                                                    weight 2 · round to Bitbucket
                                                                    GitHubnone0/10

                                                                    No evidence of migration tooling for moving code/users from another platform (e.g., GitLab, Bitbucket, SVN) or from self-hosted GitHub Enterprise Server to GitHub cloud; evidence only covers Copilot features, CLI, MCP server, and general APIs, none addressing platform migration or user/account import tooling.

                                                                      ⚑ flag
                                                                      Bitbucketfullclaimed7/10

                                                                      Bitbucket documents a free migration app to move code and users from Bitbucket Server/Data Center to Cloud, plus a Cloud Premium trial matching Data Center license user count/duration to ease migration. This directly addresses moving from self-hosted to cloud, though evidence is limited to first-party claims with no independent/hands-on corroboration and no mention of migrating from other platforms (e.g., GitHub/GitLab). Missing for 10: independent verification of the migration tool's reliability, and evidence of tooling for migrating from third-party platforms other than Bitbucket Server/Data Center.

                                                                      • [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
                                                                      • [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
                                                                      proof ↗⚑ flag

                                                                    • devops-leadInstall a self-managed instance of the platform without laborious configuration

                                                                      weight 3 · round drawn
                                                                      GitHubnone0/10

                                                                      GitHub.com is a cloud SaaS product; while GitHub Enterprise Server exists as a self-managed option in reality, the evidence pack contains no mention of a self-hosted/on-prem installable instance or any setup/configuration process for it. No docs, quickstarts, or community evidence address self-hosting installation effort, so this axis cannot be credited as delivered.

                                                                        ⚑ flag
                                                                        Bitbucketnone0/10

                                                                        The evidence only mentions migrating from self-managed Bitbucket Server/Data Center to Cloud and trial licensing (bitbucket-docs-15, bitbucket-docs-16), but provides no documentation of an actual self-managed installation process, ease of setup, or reduced configuration effort. No evidence describes install steps, deployment tooling, or admin experience for a self-hosted instance.

                                                                        • [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
                                                                        • [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
                                                                        proof ↗⚑ flag

                                                                      Not comparable on these axes

                                                                      1. ai-native userRead the product's source under an open license

                                                                        weight 2 · not comparable
                                                                        GitHubpartialclaimed3/10

                                                                        GitHub's own docs describe the GitHub CLI as 'an open source tool' (github-docs-31, github-docs-37), giving AI-native users a component of the product whose source they can read under an open license. However, the core GitHub.com platform, Copilot, and most other product components have no evidence of being open-licensed or source-available anywhere in the pack. Missing for 10: evidence that GitHub's main platform/service source is open-licensed, license details for the CLI repo, and any indication of open-sourcing beyond the CLI tool.

                                                                        • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line. When you're working from the command line, you can use…”
                                                                        • [claimed-docs] “GitHub CLI is an open source tool for using GitHub from your computer's command line.”
                                                                        proof ↗⚑ flag
                                                                        Bitbucketn/a

                                                                        Bitbucket is a proprietary closed-source SaaS/on-prem product; there is no evidence its own source code is available under an open license, and this axis is not a fair question for this kind of commercial hosted product's category — it's a category error, not a gap in an applicable capability.

                                                                          ⚑ flag