Skip to content

[plan] Schema Consistency: Address dead code and low-adoption features #8374

@github-actions

Description

@github-actions

Overview

This tracking issue addresses findings from the comprehensive schema consistency analysis in discussion #8372. The analysis identified one confirmed dead code field and five low-adoption features that need monitoring.

Source: Discussion #8372

Key Findings

Critical Issue

  • ✅ 97.4% schema-parser consistency (38/39 fields)
  • ⚠️ 1 dead code field: githubActionsStep (no implementation, no usage in 90+ workflows)

Moderate Issues

  • 5 low-adoption features (<2% usage): run-name, runtimes, runs-on, post-steps, bots
  • File naming convention variance (informational)

Planned Sub-Tasks

  1. Remove dead code field - Remove githubActionsStep from schema
  2. Document architectural patterns - Create ARCHITECTURE.md documenting 5 identified patterns
  3. Set up low-adoption monitoring - Create tracking mechanism for low-adoption features
  4. Document file naming conventions - Document dash-to-underscore convention in ARCHITECTURE.md
  5. Add deprecation guidelines - Document process for deprecating low-adoption features

Success Criteria

  • Dead code removed from schema
  • Architectural patterns documented
  • Low-adoption monitoring in place
  • Clear deprecation process documented

Timeline

  • Priority 1: Dead code removal (next breaking release v2.0+)
  • Priority 2: Documentation and monitoring setup (Q1 2025)
  • Priority 3: Quarterly reviews (Q1-Q2 2025)

AI generated by Plan Command for discussion #8372

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions