Skip to content

[q] feat(sergo): create up to 3 issues from findings labeled "sergo" #26508

@github-actions

Description

@github-actions

Updates the sergo workflow so that each run creates up to 3 GitHub issues from its top findings, automatically labeled sergo.

Changes

sergo.md

  • Added safe-outputs.create-issue block (max: 3, labels: [sergo], expires: 7d) — uses the safe-outputs mechanism required by strict mode
  • Added issues toolset to github.toolsets so the agent can search for existing issues before creating duplicates
  • Added Step 7 — instructs the agent to create at most 3 issues from top findings using create-issue, skipping any that already have an open tracking issue
  • Renumbered old steps 7 → 8 and 8 → 9, updated output requirements and success criteria accordingly

sergo.lock.yml

Recompiled automatically.

Validation

✅ sergo.md — compiled successfully, no errors, no warnings

Warning

Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.

Protected files

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.

Create the pull request manually
# Download the patch from the workflow run
gh run download 24482167873 -n agent -D /tmp/agent-24482167873

# Create a new branch
git checkout -b q/sergo-create-issues-from-findings-786be2c3088449ef main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-24482167873/aw-q-sergo-create-issues-from-findings.patch

# Push the branch and create the pull request
git push origin q/sergo-create-issues-from-findings-786be2c3088449ef
gh pr create --title '[q] feat(sergo): create up to 3 issues from findings labeled "sergo"' --base main --head q/sergo-create-issues-from-findings-786be2c3088449ef --repo github/gh-aw

🎩 Equipped by Q · ● 1.8M ·

  • expires on Apr 17, 2026, 10:49 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions