Skip to content

chore: Remove legacy testing.yml (duplicate of checks.yml) #1231

Open

Description

@ashleyshaw

Chore Summary

The .github/workflows/testing.yml workflow is a legacy duplicate of checks.yml. Running this workflow wastes ~2-3% of monthly GitHub Actions minutes by duplicating CI checks. Removing testing.yml entirely will consolidate CI infrastructure, as checks.yml is the authoritative CI workflow and covers all validation needs.

Scope / Affected Areas

  • .github/workflows/testing.yml — legacy duplicate workflow file
  • Project documentation and references to testing.yml
  • CI validation coverage verification

Steps / Checklist

  • Audit confirms testing.yml duplicates checks.yml
  • No external repos reference this workflow
  • checks.yml covers all required test scenarios
  • Delete .github/workflows/testing.yml
  • Search docs for any references to testing.yml
  • Update any references to point to checks.yml
  • Verify checks.yml has all necessary validations
  • Create PR and request review
  • Merge to develop

Acceptance Criteria

  • File .github/workflows/testing.yml is deleted
  • Git history shows clean file deletion
  • No documentation references to testing.yml remain
  • Verified no external repos depend on this workflow
  • checks.yml still covers all test scenarios
  • PR merged to develop

Additional Context

  • Parent Epic: feat: Consolidate 31 GitHub workflows for efficiency and maintainability #1227 - Consolidate 31 GitHub workflows
  • Project Documentation: .github/projects/active/workflows-consolidation-2026-q3/README.md
  • Phase 1A Guide: .github/projects/active/workflows-consolidation-2026-q3/GITHUB_ISSUE_PHASE_1A.md
  • Execution Playbook: .github/projects/active/workflows-consolidation-2026-q3/EXECUTION_PLAYBOOK.md

Effort: 1 hour | Phase: 1A - Quick Wins


Definition of Ready (DoR)

  • Audit confirms testing.yml duplicates checks.yml
  • No external repos reference this workflow
  • checks.yml covers all required test scenarios

Definition of Done (DoD)

  • Affected files and documentation updated
  • PR uses correct branch prefix (chore/)
  • Approved by at least one maintainer
  • Code changes follow repository style guidelines
  • No breaking changes
  • Manual verification: Workflows still trigger as expected

Definition of Ready (DoR)

  • Task clearly defined
  • Acceptance criteria listed
  • Related issues linked
  • Estimated effort

Definition of Done (DoD)

  • Task completed
  • Changes reviewed and merged
  • No regressions introduced
  • Documentation updated if needed

Activity

  1. linear-code commented on Jul 24, 2026

    @linear-code
  2. added this to the v1.0 milestone on Jul 24, 2026
  3. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 0 day(s)
    • SLA state: Within SLA
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-07-24T06:21:58.605Z

    Maintained by project-meta-sync workflow.

  4. 2 remaining items

  5. 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

  6. modified the milestones: v1.0, v1.1 on Aug 29, 2026
  7. 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:priority:normal
    • migrate:status:needs-review
    • migrate:type:chore
    • area:workflows

    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

Assignees

Type

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions