Repository navigation
Description
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-templateworkflow — update to referenceissue-create-enhanced
Steps / Checklist
- Review
issue-create-enhanced.ymlinput parity vsissue-create-from-template.yml(confirm all inputs covered or superseded) - Search for any references to
issue-create-from-templatein 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.ymldeleted from repository - All references updated to
issue-create-enhanced - Issue creation via
issue-create-enhanced.ymlverified 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.ymldeleted - All references updated
-
issue-create-enhanced.ymltested end-to-end - PR uses correct branch prefix (
chore/) - Approved by at least one maintainer
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Jul 29, 2026
LS-1962
github-actions commentedon Jul 29, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
ashleyshaw commentedon Aug 7, 2026
✅ 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:
Status: Ready for execution. Refer to coordination deadlines in action plan.
ashleyshaw commentedon Aug 7, 2026
📋 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
🔗 Quick Links
Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com
Copilot commentedon Aug 29, 2026
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)
github-actions commentedon Sep 3, 2026
Unchecked DoD items found. Please complete all checklist items before closing this issue.
To close this issue:
To force close this issue without completing DoD:
meta:force-closelabelFor more information on Definition of Done standards, see the issue template guide: https://github.com/lightspeedwp/.github/issues/new/choose
github-actions commentedon Sep 3, 2026
Milestone Allocation
github-actions commentedon Sep 3, 2026
✅ Issue checklists finalised after closure.
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:status:readymigrate:type:chorepriority:lowstatus:ready-for-developmentValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.