/
/
Find the commits behind a new Bugsnag error
For developers who want suspect Azure DevOps commits for a Bugsnag error, just by asking their AI assistant.
On this page
Connector
Connect Azure DevOps, pick your AI tool and paste the prompt.
The problem
Which change introduced this error
Working out which change introduced a Bugsnag error means reading the first seen time in one tool and scrolling commit history, pushes and builds in another. It is slow and the answer is easy to get wrong.
Without PopdockAI
- Note when the error was first seen in Bugsnag
- Scroll Azure DevOps commits and pushes before it
- Check which builds went out
- Guess at the culprit
With PopdockAI
- The error's first seen time is read
- Commits, pushes and builds in the window before are listed
- Candidates are ranked by how closely they fit
- The evidence is described as circumstantial, and the window is not widened quietly
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find which Azure DevOps commits in repository {repository-id} landed shortly before Bugsnag error {error-id} first appeared, looking back {window-days} days (default 3).
**Step 1: Read the error (Bugsnag)**
Call `bugsnag-get-error` with `error-id`. Note `first-seen-date`, `error-class`, `message` and `status`. If nothing returns, stop. Then call `bugsnag-get-event` with `error-id` and `max-records` 5 and note `app-version`, `app-release-stage` and `file`.
**Step 2: Find the commits (Azure DevOps)**
Call `azure-devops-get-commit` with `repository-id`, `author-date.from` set to the first-seen date minus the window and `author-date.to` set to the first-seen date. Call `azure-devops-get-push` with `repository-id`, `date.from` and `date.to` for the same window.
**Step 3: Rank**
Mark a commit as stronger when its comment names the error class, the file from the event, or a work item that mentions the error. Call `azure-devops-get-build` with `repository-id` to show whether builds finished in the window and with what result.
**Step 4: Report**
First-seen time, the event version and stage, then up to 10 commits (commit-id, author-name, author-date, comment, why ranked) and the builds in the window. State clearly that this is circumstantial, a time-window match and not proof of cause.
**Rules & Guidelines:**
* Tools prefixed azure-devops are on the Azure DevOps server; tools prefixed bugsnag are on the Bugsnag server. Both must be connected.
* Read-only job. Never call `bugsnag-link-error-issue`, `bugsnag-create-error-issue`, `bugsnag-assign-error`, `bugsnag-fix-error`, `bugsnag-ignore-error`, `bugsnag-discard-error`, `bugsnag-open-error`, `bugsnag-update-error-severity`, `bugsnag-update-project`, `bugsnag-add-project` or `bugsnag-add-project-collaborator`. The Azure DevOps server has no write tools.
**Validation:**
* If the error has no first-seen date or no commits fall in the window, say so and do not widen the window silently.
* Date formats may differ between systems; normalise to UTC before comparing.Who it's for
One answer, three teams that use it
Developers
Start debugging from the likely change
Ranked candidates tell you which commits to read first when a new error appears.
Which commits in Fabrikam.Api came just before Bugsnag error 7a1c903e first appeared?
On call engineers
Decide whether to roll back
See the builds and pushes before an error first appeared, to judge if a recent deploy caused it.
What was pushed and built in Northwind.Portal before Bugsnag error 5f2e11aa was first seen?
Engineering managers
Route an error to the right person
The likely change points to the author best placed to fix it.
Find suspect Azure DevOps commits for Bugsnag error 3d9b2c71 in Contoso.Services.
How it works
What PopdockAI does when you ask
You give an error and a repository, and your AI assistant ranks the changes that came just before it. It creates and changes nothing.
01
Ask
You give the Bugsnag error id and repository.
02
Read
It reads when the error was first seen.
03
Search
It lists Azure DevOps commits, pushes and builds in the window before.
04
Report
You get ranked candidates, with a note that the evidence is circumstantial.
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.
bugsnag-get-error
bugsnag-get-event
azure-devops-get-commit
azure-devops-get-push
azure-devops-get-build
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
A ranked list of suspect changes
Related use cases
More ways to put this data to work
Find Azure DevOps work items for a Bugsnag error
Ask your AI whether a Bugsnag error has an Azure DevOps work item and it searches by id, class and message, then gives a tracked or untracked verdict.
Learn More
Diagnose failing Azure DevOps builds
Ask your AI to diagnose a failing Azure DevOps pipeline and it finds the first failing run and the commits since the last success, with likely causes ranked.
Learn More
Summarize Azure DevOps repository activity
Ask your AI to summarise repository activity and it reports commits, pushes, pull requests, contributors and diverged branches over a window.
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
Audit stale Azure DevOps work items
Ask your AI to audit a project and it flags unassigned, untouched and neglected priority 1 work items grouped by area. Nothing is reassigned or closed.
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.