Skip to content

Standardize issue-title-prefix vs title-prefix #437

Closed

Description

@strawgate
No description provided.

Activity

  1. github-actions commented on Feb 27, 2026

    @github-actions
    Contributor

    TL;DR: the inconsistency is real and localized—scheduled-audit/scheduled-fix use issue-title-prefix while most other workflows use title-prefix; I recommend standardizing on title-prefix with a short compatibility window to avoid breaking existing consumers.

    Recommendation

    Adopt title-prefix as the canonical input name across workflows, and treat issue-title-prefix as a deprecated alias for one release cycle (if backward compatibility is needed). This aligns scheduled workflows with the dominant existing interface (inputs.title-prefix appears 36 times vs inputs.issue-title-prefix 6 times in .github/workflows/gh-aw-*.md).

    Findings
    • Confirmed mismatch in scheduled base workflows:
      • .github/workflows/gh-aw-scheduled-audit.md:30 defines issue-title-prefix
      • .github/workflows/gh-aw-scheduled-fix.md:30 defines issue-title-prefix
    • Those files also reference inputs.issue-title-prefix in runtime wiring:
      • .github/workflows/gh-aw-scheduled-audit.md:61,79,87
      • .github/workflows/gh-aw-scheduled-fix.md:66,87,117
    • Shared fragment and broader workflow ecosystem use title-prefix:
      • .github/workflows/gh-aw-fragments/previous-findings.md:6 uses inputs.title-prefix
      • Many workflows use ${{ inputs.title-prefix }} (36 matches across .github/workflows/gh-aw-*.md)
    • User-facing docs/examples for scheduled workflows currently expose the issue-title-prefix variant:
      • gh-agent-workflows/scheduled-audit/README.md:37
      • gh-agent-workflows/scheduled-fix/README.md:36
      • gh-agent-workflows/scheduled-audit/example.yml:17
      • gh-agent-workflows/scheduled-fix/example.yml:17
    • Related history:
      • Issue #405 requested stronger dedup and configurable prefixing.
      • PR #406 introduced previous-findings + configurable prefixes, and explicitly left scheduled workflows scoped to inputs.issue-title-prefix while others used inputs.title-prefix.
    Verification

    I ran targeted verification in the workspace:

    $ grep -nE "issue-title-prefix|title-prefix" .github/workflows/gh-aw-scheduled-audit.md .github/workflows/gh-aw-scheduled-fix.md .github/workflows/gh-aw-fragments/previous-findings.md gh-agent-workflows/scheduled-audit/README.md gh-agent-workflows/scheduled-fix/README.md gh-agent-workflows/scheduled-audit/example.yml gh-agent-workflows/scheduled-fix/example.yml
    .github/workflows/gh-aw-scheduled-audit.md:30:      issue-title-prefix:
    .github/workflows/gh-aw-scheduled-audit.md:61:  group: scheduled-audit-${{ inputs.issue-title-prefix }}
    .github/workflows/gh-aw-scheduled-audit.md:79:    title-prefix: "${{ inputs.issue-title-prefix }} "
    .github/workflows/gh-aw-scheduled-audit.md:87:      TITLE_PREFIX: ${{ inputs.issue-title-prefix }}
    .github/workflows/gh-aw-scheduled-fix.md:30:      issue-title-prefix:
    .github/workflows/gh-aw-scheduled-fix.md:66:  group: scheduled-fix-${{ inputs.issue-title-prefix }}
    .github/workflows/gh-aw-scheduled-fix.md:87:      TITLE_PREFIX: ${{ inputs.issue-title-prefix }}
    .github/workflows/gh-aw-scheduled-fix.md:117:github-search_issues: query="repo:{owner}/{repo} is:issue is:open in:title \"${{ inputs.issue-title-prefix }}\" sort:updated-asc"
    .github/workflows/gh-aw-fragments/previous-findings.md:6:      TITLE_PREFIX: ${{ inputs.title-prefix }}
    gh-agent-workflows/scheduled-audit/README.md:37:| `issue-title-prefix` | ...
    gh-agent-workflows/scheduled-fix/README.md:36:| `issue-title-prefix` | ...
    gh-agent-workflows/scheduled-audit/example.yml:17:      issue-title-prefix: "[my-audit]"
    gh-agent-workflows/scheduled-fix/example.yml:17:      issue-title-prefix: "[my-audit]"
    
    $ grep -Rno "inputs\.title-prefix" .github/workflows/gh-aw-*.md | wc -l
    36
    $ grep -Rno "inputs\.issue-title-prefix" .github/workflows/gh-aw-*.md | wc -l
    6

    Best-of-three check: I ran 3 independent sub-investigations (audit-first, history-first, grep-first). Two converged on “standardize naming”; one interpreted this as “feature already implemented” (dedup is implemented) but did not invalidate the naming inconsistency evidence above.

    Detailed Action Plan
    1. Canonicalize scheduled workflow inputs to title-prefix
      • Update input keys and all references in:
        • .github/workflows/gh-aw-scheduled-audit.md (30, 61, 79, 87)
        • .github/workflows/gh-aw-scheduled-fix.md (30, 66, 87, 117)
    2. Backward compatibility (recommended)
      • For one release, accept both names in scheduled workflows (map legacy issue-title-prefix to canonical title-prefix internally) and document deprecation.
    3. Update user-facing docs/examples
      • gh-agent-workflows/scheduled-audit/README.md:37
      • gh-agent-workflows/scheduled-fix/README.md:36
      • gh-agent-workflows/scheduled-audit/example.yml:17
      • gh-agent-workflows/scheduled-fix/example.yml:17
    4. Recompile generated workflow artifacts
      • Run make compile so .lock.yml outputs reflect the source rename.
    5. Validate and ship
      • Run make lint
      • Verify no unintended remnants via grep for both prefixes
      • Note migration/deprecation in release notes.
    Related Items
    Type Link Relevance
    Issue #437 Current triage target
    Issue #405 Origin of previous-findings/prefix configurability work
    PR #406 Implemented dedup + mixed prefix naming pattern
    File .github/workflows/gh-aw-fragments/previous-findings.md:6 Uses inputs.title-prefix
    File .github/workflows/gh-aw-scheduled-audit.md:30 Uses issue-title-prefix
    File .github/workflows/gh-aw-scheduled-fix.md:30 Uses issue-title-prefix

    What is this? | From workflow: Issue Triage

    Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions