/
/
Spot branches that exist on only one side
For developers who mirror code between Azure DevOps and GitHub and want branch drift found, by asking their AI assistant.
On this page
Connector
Connect Azure DevOps, pick your AI tool and paste the prompt.
The problem
Mirrored branch lists drift apart
Branch lists in Azure DevOps and GitHub drift apart when a repository is mirrored. Stale or missing branches are found only by putting the two lists side by side and checking them by eye.
Without PopdockAI
- List branches in Azure DevOps
- List branches in GitHub
- Compare the names by eye
- Miss a branch that never mirrored
With PopdockAI
- Branch lists are read from both systems
- Names are matched across the two
- Branches on only one side are listed
- Empty or truncated sides are noted, and nothing is written
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Compare the branches of Azure DevOps repository `{repository-id}` with the branches of GitHub company `{company}`, optionally limited to names containing `{name-filter}`.
**Step 1: Azure DevOps branches**
Call `azure-devops-get-git-ref` with repository-id `{repository-id}` and name.contains `{name-filter}` if given. Then call `azure-devops-get-branch-stat` for the same repository to get ahead counts and latest commit author. Strip the refs/heads/ prefix from names.
**Step 2: GitHub branches**
Call `github-get-branch` with company `{company}` and name.contains `{name-filter}` if given. Note which are protected.
**Step 3: Match across servers**
Match by branch name after stripping refs/heads/. Treat names as case-sensitive; flag names differing only by case.
**Step 4: Report**
Table of branch, in Azure DevOps, in GitHub, ahead count, protected on GitHub. List stale candidates: branches on only one side.
**Rules & Guidelines:**
* Tools prefixed azure-devops- belong to the azure-devops server; tools prefixed github- belong to the github server. Both servers must be connected.
* This prompt is read-only. Never call github-add-issue, github-update-issue, github-add-issue-comment, github-add-issue-label, github-add-issue-assignee, github-lock-issue, github-unlock-issue, github-rerun-workflow-run, github-cancel-workflow-run, github-enable-workflow, github-disable-workflow, github-add-milestone or github-update-milestone.
**Validation:**
* If one side returns no branches, say so and stop the comparison there.
* Report truncation by max-records as a partial result.Who it's for
One answer, three teams that use it
DevOps engineers
Keep a mirror honest
Branches present on only one side are listed, so drift is fixed on purpose.
Which branches exist in Fabrikam.Api in Azure DevOps but not fabrikam/api on GitHub?
Developers
Find where your branch went
Check whether a branch made it to the other system before you share it.
Reconcile the branches of Northwind.Portal with northwind/portal on GitHub.
Migration leads
Confirm a repository move
Make sure every branch arrived after moving between Azure DevOps and GitHub.
Compare branch lists for Contoso.Services and contoso/services and list anything missing.
How it works
What PopdockAI does when you ask
You name the repository on each side and your AI assistant compares their branches. It only reads, and GitHub write actions are off limits.
01
Ask
You name the Azure DevOps repository and its GitHub counterpart.
02
Read
It reads the branch lists from both systems.
03
Compare
It matches names and finds the branches on one side only.
04
Report
You get each list, with a note if a side was empty or truncated.
What PopdockAI provides
The tools behind the answer
Ready made tools for Azure DevOps and one secure connection to your AI tool. No code, no exports.
azure-devops-get-git-ref
azure-devops-get-branch-stat
github-get-branch
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
See which branches exist on one side only
Related use cases
More ways to put this data to work
Compare Azure DevOps and GitHub CI health
Ask your AI to compare CI health for a branch and it lines up recent Azure DevOps builds with GitHub workflow runs, flagging where they disagree.
Learn More
Reconcile Azure DevOps and GitHub commits
Ask your AI to reconcile commits between an Azure DevOps repository and GitHub and it lists those missing on either side. Read-only on both.
Learn More
Reconcile Azure DevOps work items with GitHub issues
Ask your AI to reconcile Azure DevOps work items with GitHub issues and it lists the unmatched items and stale references. Read-only on both.
Learn More
Trace an Azure DevOps work item to GitHub
Ask your AI to trace a work item to GitHub and it builds one merged timeline of Azure DevOps comments and GitHub issues and commits.
Learn More
Audit Azure DevOps branch hygiene
Ask your AI to audit a repository and it lists stale, locked and diverged Azure DevOps branches with a suggested action for each. Nothing is deleted or locked.
Learn More
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.