Skip to content

Phase 4.5: Delete issue-create-from-template.yml (superseded by issue-create-enhanced.yml) #1410

Description

@ashleyshaw

Chore Summary

issue-create-enhanced.yml (added in PR #1377) supersedes issue-create-from-template.yml. Both workflows accept the same template_key options (identical choice list) and perform the same core function of creating issues with correct templates. The enhanced version adds additional inputs and improved error handling.

Delete the legacy issue-create-from-template.yml to eliminate the duplication.

Part of epic #1227 — Workflows Consolidation Initiative. Net: −1 workflow.

Scope / Affected Areas

  • .github/workflows/issue-create-from-template.yml — delete
  • Any documentation or agent prompts referencing issue-create-from-template workflow — update to reference issue-create-enhanced

Steps / Checklist

  • Review issue-create-enhanced.yml input parity vs issue-create-from-template.yml (confirm all inputs covered or superseded)
  • Search for any references to issue-create-from-template in agents, prompts, workflows, and docs
  • Update references to point to issue-create-enhanced
  • git rm .github/workflows/issue-create-from-template.yml
  • Commit: chore(ci): delete issue-create-from-template.yml (superseded by issue-create-enhanced.yml, #1377)

Acceptance Criteria

  • issue-create-from-template.yml deleted from repository
  • All references updated to issue-create-enhanced
  • Issue creation via issue-create-enhanced.yml verified working
  • Workflow count reduces by 1

Additional Context

Dependency: Independent of other Phase 4 sub-phases. Can run immediately after confirmation.

Added context: PR #1377 introduced issue-create-enhanced.yml as a more capable replacement with additional input parameters and improved template resolution logic.

See: .github/projects/active/workflows-consolidation-2026-q3/PHASE_4_PLANNING.md


Definition of Ready (DoR)

  • Task/goal described and scoped
  • Confirms it does not fit the Code Refactor or Maintenance templates
  • Acceptance criteria listed
  • Input parity review complete

Definition of Done (DoD)

  • issue-create-from-template.yml deleted
  • All references updated
  • issue-create-enhanced.yml tested end-to-end
  • PR uses correct branch prefix (chore/)
  • Approved by at least one maintainer

Activity

  1. linear-code commented on Jul 29, 2026

    @linear-code
  2. github-actions commented on Jul 29, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 8 day(s)
    • SLA state: SLA risk
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-07T14:36:06.999Z

    Maintained by project-meta-sync workflow.

  3. added theissue type on Aug 7, 2026
  4. added this to the v1.0 milestone on Aug 7, 2026
  5. self-assigned this
    on Aug 7, 2026
  6. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    ✅ Phase 4 planning complete: PR #1631 merged to develop

    All Phase 4 planning documents, specifications, and coordination timelines are now available in the merged PR. This issue is ready for execution per the CONSOLIDATED_ACTION_PLAN_2026_08_07.md timeline.

    See merged PR #1631 for:

    • OPENSPEC_WORKFLOW_CONSOLIDATION.md (formal specification)
    • CONSOLIDATED_ACTION_PLAN_2026_08_07.md (execution timeline & blockers)
    • GITHUB_ISSUES_PHASE_4_TEMPLATES.md (implementation steps)
    • Detailed risk mitigation and testing protocols

    Status: Ready for execution. Refer to coordination deadlines in action plan.

  7. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    📋 Project Planning Update — workflows-consolidation-2026-q3

    This issue is related to the workflows-consolidation-2026-q3 active project.

    📁 Project Documentation

    ✅ Phase 1-3 Summary

    Comprehensive audits (Phase 1), planning standardization (Phase 2), and OpenSpec RFC generation (Phase 3) have been completed for this project. Full documentation available in the project directory.

    🎯 Recommended Actions

    1. Review Project Documentation for overview and timeline
    2. Consult OpenSpec RFC for implementation roadmap
    3. Check Related Issues for dependencies and prerequisites
    4. Reference Phase Documents for specific execution guidance

    🔗 Quick Links


    Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com

  8. modified the milestones: v1.0, v1.1 on Aug 29, 2026
  9. Copilot commented on Aug 29, 2026

    Copilot
    Contributor

    The agent encountered an error and was unable to start working on this issue: The rate limit was exceeded. Please try again in a few minutes. (Request id: F75C:24232F:8F8B8CC:757A058:6A92FFBA)

  10. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor

    ⚠️ This issue was closed but the Definition of Done (DoD) is not complete.

    Unchecked DoD items found. Please complete all checklist items before closing this issue.

    To close this issue:

    • ✅ Complete all DoD checklist items and check them off
    • 🔁 Close the issue again

    To force close this issue without completing DoD:

    • Add the meta:force-close label
    • The system will then allow closure

    For more information on Definition of Done standards, see the issue template guide: https://github.com/lightspeedwp/.github/issues/new/choose

  11. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor

    Milestone Allocation

    
    
  12. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor

    ✅ Issue checklists finalised after closure.

  13. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:status:ready
    • migrate:type:chore
    • priority:low
    • status:ready-for-development

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

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

Metadata

Metadata

Type

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions