githubnext/gh-aw

AI Summary: This issue aims to achieve 100% GitHub Action pinning compliance by identifying and updating the single remaining unpinned action to its commit SHA. This crucial step enhances supply chain security by ensuring only verified action versions are used. The issue provides a clear, step-by-step guide for identifying the action, finding its SHA, and updating the relevant workflow file.

AI Summary: This issue proposes logging the `actionlint` version on its first execution to improve debugging and reproducibility. The approach involves executing a Docker command to retrieve the version, displaying it using a formatted info message, and caching the result to prevent repeated calls.

AI Summary: This issue proposes enhancing actionlint's user-facing messages to explicitly state that it includes shellcheck and pyflakes validation. The goal is to clarify the full scope of actionlint's checks by updating progress messages in `pkg/cli/actionlint.go` and relevant documentation. The proposed change is to append "(includes shellcheck & pyflakes)" to the "Running actionlint" message.

AI Summary: This issue proposes adding a `make actionlint` target to simplify local validation of GitHub workflows using `actionlint`. This will improve developer experience by providing an easy-to-discover and consistent command for contributors, replacing the need to remember the full `gh aw compile --actionlint` command.

AI Summary: This GitHub issue reports an inconsistency in the help text for three specific commands (`mcp-server`, `secrets bootstrap`, and `update`). The short descriptions for these commands incorrectly use "gh-aw" instead of the consistent "gh aw" format, which matches how users invoke the CLI. The issue requests updating these descriptions to use "gh aw" for better clarity and consistency.

AI Summary: This GitHub issue identifies an inconsistency in the capitalization of "markdown" within the CLI's help text, where it is often used in lowercase instead of the correct "Markdown". The issue argues that "Markdown" is a proper noun and should always be capitalized for consistency, providing specific examples of incorrect and correct usage across multiple files. This is flagged as a low-priority task aimed at improving overall CLI consistency.

AI Summary: This issue proposes removing the `github.com/mattn/go-isatty` dependency from the `SpinnerWrapper` as it's now redundant. The underlying `spinner` library (v1.23.1+) has switched to `golang.org/x/term` for TTY detection, making the direct `go-isatty` import unnecessary. The task involves either replacing the `go-isatty` call with `golang.org/x/term` or allowing the spinner library to handle TTY detection internally.

AI Summary: This GitHub issue proposes adding a clear explanation to the documentation about why GitHub Actions workflows need to be compiled from Markdown to YAML. The goal is to help beginners understand that the human-friendly `.md` file is translated into the machine-readable `.yml` format required by GitHub Actions, addressing confusion where users might mistake the Markdown file for the workflow itself. The solution involves adding a dedicated "Why Compile?" section to the quick-start guide.

AI Summary: This issue aims to enhance the Quick Start documentation by adding clear "Expected output" sections after installation and verification commands. The goal is to provide beginners with success indicators, helping them confirm if commands executed successfully. The task involves modifying `docs/src/content/docs/setup/quick-start.md` with specific examples of successful command output.

AI Summary: This GitHub issue proposes adding a new, simpler "Hello World" workflow example to the Quick Start guide. This basic example, which will create and close a GitHub issue, aims to provide a gentler introduction for beginners before they encounter the more complex "Daily Team Status" workflow. The existing complex example will be retained but positioned as a subsequent "real-world" example.

AI Summary: This GitHub issue highlights inconsistent terminology across various CLI commands when referring to workflows. Terms like "workflow-id", "workflow-base-name", and "pattern" are used interchangeably, causing confusion. The goal is to standardize on a single, clear term such as "workflow-id" or "workflow-name" for all affected commands and their help texts.