Skip to content

[plan] Document concurrency group pattern in create-agentic-workflow.md #29784

Closed as not planned

Description

@github-actions

Objective

Add a section on the concurrency group pattern to .github/aw/create-agentic-workflow.md to prevent duplicate comments on force-pushes and rapid CI reruns.

Context

From discussion #29782 — Agent Persona Exploration found that none of the 4 tested scenarios included a concurrency group. Without it, workflows can post duplicate comments on force-pushes or rapid CI reruns.

Approach

  1. Open .github/aw/create-agentic-workflow.md
  2. Add a dedicated Preventing Duplicate Actions section that explains when concurrency is needed
  3. Include the standard pattern:
concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
  cancel-in-progress: true
  1. Note when cancel-in-progress: false may be preferable

Files to Modify

  • .github/aw/create-agentic-workflow.md

Acceptance Criteria

  • A concurrency group section exists in create-agentic-workflow.md
  • The standard pattern is shown with explanation
  • Documentation explains when to use cancel-in-progress: true vs false

Generated by Plan Command for issue #discussion #29782 · ● 313.9K · ◷

  • expires on May 4, 2026, 3:56 PM UTC

Activity

  1. github-actions commented on May 3, 2026

    @github-actions
    ContributorAuthor

    🍪 Issue Monster selected this for Copilot

    I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

    If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ● 18.1K · ◷

  2. github-actions commented on May 4, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-05-04T15:56:33.968Z.

    Closed by Workflow

  3. github-actions commented on May 4, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-05-04T15:56:33.968Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions