Write

Track every broken GitHub workflow with exactly one issue

For developers who want a CI break recorded once with its evidence, instead of three duplicate issues, by asking their AI assistant.

Report a failed GitHub workflow as an issue

Open an issue for the failing CI workflow on main in contoso/web, unless one already exists.

CI on main has failed 4 runs in a row, and no open issue tracks it, so I drafted a new one. - First failure: run 4802, commit e4f5a6b by Jordan Lee - Latest failure: run 4819, 6 October - Labels: ci, bug, both already in use Shall I create this issue?

GitHub

Sample figures. Your results come from your own account.

github-get-workflow-run

github-get-issue

github-get-issue-label

github-add-issue-comment

github-add-issue

github-get-workflow

On this page

The problem

The prompt

Who it's for

How it works

Tools used

Connector

GitHub

Run it on your own GitHub data.

Connect GitHub, pick your AI tool and paste the prompt.

The problem

Everyone assumes someone else filed the CI break

A broken GitHub Actions workflow should be tracked as one issue, but each person who notices opens a new one or assumes someone else did. Gathering the failing run, suspect commit and streak length takes time mid sprint.

Without PopdockAI

Notice the red workflow
Search for an existing issue, or not
Work out when it started failing
Open a duplicate issue

With PopdockAI

The latest run is confirmed failed and the streak counted
An open issue tracking the workflow is looked for
A comment or new issue is drafted with only labels in use
You approve the draft and it writes once

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt

**Objective:** Make sure the latest failure of the workflow `{workflow-name}` in `{repository}`, on branch `{branch}` (default the repository's main branch), is tracked by exactly one open issue.

**Step 1: Confirm it is failing**

Call `github-get-workflow-run` with company `{repository}`, name `{workflow-name}`, branch `{branch}` when given, and max-records 20. Take the most recent run. If its conclusion is not `failure`, report its status and conclusion and stop; there is nothing to raise.

**Step 2: Gather the evidence**

From the failing run take run-number, url, sha, commit-message, commit-author-name and triggering-event. Walk back through the runs to find the last `success` and count the consecutive failures since.

**Step 3: Look for an existing issue**

Call `github-get-issue` with company `{repository}`, status `open`, and title.contains `{workflow-name}`. If one clearly tracks this workflow failing, it is the existing issue.

**Step 4: Draft and confirm**

* If an issue exists, draft a comment with the new run-number, url, sha and consecutive-failure count.
* If none exists, draft an issue titled "{workflow-name} failing on <branch>" with a body listing the first failing run, the latest failing run, the suspect commit (sha, author, message), and the run urls. Propose a label only from `github-get-issue-label` label-name values already in use.

Show the draft and ask the user to confirm.

**Step 5: Write once**

After confirmation, call `github-add-issue-comment` once on the existing issue, or `github-add-issue` once for the new one. Report the issue-number.

**Rules & Guidelines:**

* Never create a second issue when an open one already tracks this workflow.
* Do NOT call `github-rerun-workflow-run`, `github-cancel-workflow-run`, `github-disable-workflow` or `github-update-issue`.
* The tools do not return job logs; link the run url rather than guessing the error.

**Validation:**

* If no runs are returned, check the workflow name with `github-get-workflow` using name.contains and list the close matches.
* If more than one open issue could be the tracker, list them and ask which to comment on.

Who it's for

One answer, three teams that use it

Developers

Report a broken build properly

The first and latest failures and the suspect commit go into the issue for you.

Open an issue for the failing Lint workflow on main in fabrikam/app if none exists.

DevOps engineers

Keep the CI issue up to date

New failing runs are added as comments to the existing issue, not as new issues.

Update the issue tracking the Build workflow in contoso/api with the latest failed run.

Tech leads

See how long the build has been red

The count of consecutive failures since the last success shows how urgent it is.

How long has the Deploy workflow been failing in northwind/platform? Report it as an issue.

How it works

What PopdockAI does when you ask

You name the workflow and optionally a branch, and your AI assistant drafts the right update. It links run pages rather than guessing at errors.

Ask

You name the workflow and optionally a branch.

Your AI tool

Check

It confirms the latest run failed and counts failures since the last success.

github-get-workflow-run

github-get-workflow

It looks for an open issue tracking the workflow and drafts a comment or new issue.

github-get-issue

github-get-issue-label

Confirm

You approve the draft and it writes once.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for GitHub and one secure connection to your AI tool. No code, no exports.

get-data

github-get-workflow-run

Returns GitHub Actions workflow runs with their status and conclusion. Filter by workflow name, run number, branch, triggering event, status, conclusion and created date range.

get-data

github-get-issue

Returns GitHub issues from a repository. Filter by issue number, title text, state, labels, assignee, author, milestone, and created or updated date range.

get-data

github-get-issue-label

Returns the labels applied to GitHub issues. Filter by issue number or label name.

run-action

github-add-issue-comment

Posts a comment on a GitHub issue or pull request, identified by issue number.

run-action

github-add-issue

Opens a new issue in a GitHub repository. Takes a title, and optionally a body, an assignee, a label and a milestone number.

get-data

github-get-workflow

Returns the GitHub Actions workflows defined in a repository. Filter by name, file path and state (active or disabled).

Read only.Nothing in GitHub Changes

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

One issue per CI break, kept current

Related use cases

More ways to put this data to work

File a GitHub issue for a failed Ghost Inspector suite run

Ask your AI to file a failed Ghost Inspector suite run in GitHub and it drafts a new issue or a comment on an existing one, then links back after you confirm.

Learn More

Close GitHub issues for fixed Bugsnag errors

Ask your AI to close GitHub issues for fixed Bugsnag errors and it pairs them by exact error id, then comments and closes only the issues you confirm.

Learn More

Diagnose failed GitHub workflow runs

Ask your AI to diagnose failed GitHub workflow runs and it finds the last success and breaking commit for each workflow and branch, labelling flaky and fixed ones.

Learn More

Escalate a GitHub issue to Jira

Ask your AI to escalate a GitHub issue to Jira and it checks for an existing link, creates one Jira issue after you confirm, and links and comments both ways.

Learn More

File a GitHub issue for a Bugsnag error

Ask your AI to file a GitHub issue for a Bugsnag error and it checks for an existing issue, drafts the body from the error's details, and links it back after you confirm.

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.