Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Integrate github/gh-aw for workflow/action inspection in dev-tools #348

Copy link
Copy link

Description

@coisa
Issue body actions

Objective

Integrate github/gh-aw to improve local inspection and maintenance of workflow and action inputs before/after runs.

Current Limitation

Action workflows are currently observed only through GitHub-side context in several scenarios, which reduces confidence in local reproducibility and slows review of workflow wiring changes.

Proposed Work

  • Evaluate and adopt github/gh-aw as part of the dev-tools action-inspection flow.
  • Add usage docs and examples that show how gh-aw can inspect workflows/actions used in this repo.
  • Integrate this usage into contributor docs for faster validation of action inputs and metadata.
  • Ensure the flow is safe for CI review without requiring external mutable state.

Scope

  • In-scope: documentation, local verification workflow command examples, and optional lightweight helper scripts.
  • Out-of-scope: replacing existing CI orchestration primitives in this milestone.

Non-goals

  • Do not add invasive changes to runtime command behavior that are unrelated to workflow inspection.
  • Do not introduce a new CI dependency stack unless justified by measurable validation coverage.

Acceptance Criteria

Delivery Criteria

  • github/gh-aw usage is documented for inspecting workflows and action references in dev-tools.
  • A repeatable local runbook exists for at least one action-related review use case.
  • The recommendation includes expected output or interpretation notes.

Architectural / Isolation Criteria

  • MUST: The affected command/controller layer MUST act only as an orchestrator.
  • MUST: The solution MUST avoid tight coupling between core behavior and CLI or framework-specific I/O.
  • MUST: Responsibilities MUST be separated across input resolution, domain logic, processing or transformation, and output rendering when the change is non-trivial.
Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Status
    Backlog
    Show more project fields

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.