Connect Azure DevOps
Sign in with your Microsoft account in the browser, or use a personal access token from Azure DevOps. GitTree talks to dev.azure.com and to Microsoft’s profile service to find your organisations, then lists their repositories, pull requests and pipelines.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: hosting integrations are part of Pro.
- An Azure DevOps organisation your Microsoft account belongs to.
Where to find it
- Preferences › Integrations › Connected accounts: Connect Azure DevOps….
| Action | macOS | Windows and Linux |
|---|---|---|
| Preferences | ⌘, | Ctrl+, |
Steps
Start connecting
Choose Connect Azure DevOps….
Sign in with Microsoft
Choose Sign In with Azure DevOps, sign in with your Microsoft account in the browser and accept. The browser brings you back to GitTree.
Or use a token
Choose Enter a Personal Access Token…; Scopes the token needs lists what the token must allow.
Clone or open a repository
Your organisations’ repositories now appear when you clone, and pull requests and pipelines appear for repositories hosted there.
Expected result
Azure Repos, pull requests and Azure Pipelines appear in GitTree.
Azure DevOps pull requests
Reviewers are entered as identity ids. Set Auto-complete asks Azure DevOps to complete a pull request once every required policy passes; Azure DevOps decides when you merge, and nothing in GitTree bypasses a policy.
If something goes wrong
“This account has no repositories or organisations to list.”
The Microsoft account is not a member of an Azure DevOps organisation, or the token cannot read it. Check the organisation’s users, or create the token in the right organisation.
Questions
Does this work with Azure DevOps Server on-premises?
GitTree talks to dev.azure.com. Check the Integrations tab of the Feature Guide for what your repository’s host supports.