> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/integrations/other-git-providers.md). # Other Git providers Bitbucket and Azure DevOps support in Argos, and how to use Argos with an unsupported Git provider. Argos integrates natively with [GitHub](/docs/learn/integrations/github-integration.md) and [GitLab](/docs/learn/integrations/gitlab-integration.md). Other providers are not supported yet. ### Bitbucket Argos does not support Bitbucket Cloud or Bitbucket Data Center. If a Bitbucket integration would be valuable to your team and you are open to partnering with us on its development, [contact us](https://argos-ci.com/contact). ### Azure DevOps Argos does not support Azure DevOps. If an Azure DevOps integration would be valuable to your team and you are open to partnering with us on its development, [contact us](https://argos-ci.com/contact). ### Use Argos without a native integration You can still run visual tests from any CI system: upload screenshots with `ARGOS_TOKEN` and review builds in the Argos dashboard. Without a native integration, Argos cannot post commit statuses or pull request comments on your provider, so you review changes in Argos directly. Follow the [Quickstart](/docs/quickstart.md) to set up your project, and see the [CLI reference](/docs/reference/argos-command-line-interface-cli.md) for upload options. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://argos-ci.com/docs/learn/integrations/other-git-providers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.