Skip to content

[step-names] Align step names in release.lock.yml — mixed capitalization and dash-separator anti-pattern #28625

@github-actions

Description

@github-actions

Step Name Alignment Issues

Found in: .github/workflows/release.lock.yml

Summary

Two step names in the release workflow deviate from the established naming conventions used consistently across 200+ other lock files.

Issues Identified

1. [Medium Priority] Mixed capitalization: "Compute release Config"

Current step name:

  • Line 1058: Compute release Config

Issue:
Within a single step name, "release" is lowercase while "Config" is capitalized. This is inconsistent. All other step names that reference configuration artifacts use a uniform casing:

  • Write Safe Outputs Config — all words of the artifact name capitalized
  • Generate Safe Outputs MCP Server Config — same pattern
  • Clear MCP Config for detection — "MCP Config" capitalized as a proper artifact name
  • Save agent config folders for base branch restoration — "config" lowercase when used as a common noun

The word "release" here is an adjective modifying "Config" (a proper artifact name), so it should be capitalized to match.

Suggested improvement:

  • Compute release ConfigCompute Release Config

2. [Medium Priority] Dash-separator anti-pattern: "Notify - run sync actions and merge PR"

Current step name:

  • Line 1252: Notify - run sync actions and merge PR

Issue:
This step name uses a - dash separator, a pattern used in workflow names (e.g., "Poem Bot - A Creative Agentic Workflow") but not in step names. Every other step name in the codebase uses an imperative verb + noun phrase without separators. The - makes it look like two separate descriptions joined together, which is inconsistent with the naming style.

Suggested improvements:

  • Trigger sync and merge PR
  • Notify and merge PR
  • Run sync actions and merge PR

Agentic Task Description

To fix these step names:

  1. Update the source — Edit .github/workflows/release.md to change the step names in the relevant steps
  2. Recompile — Run gh aw compile .github/workflows/release.md to regenerate release.lock.yml
  3. Verify — Confirm the step names appear correctly in the generated lock file

Related Files

  • Source workflow: .github/workflows/release.md
  • Compiled workflow: .github/workflows/release.lock.yml
  • Project glossary: docs/src/content/docs/reference/glossary.md

Priority

This issue is Medium Priority — no functional impact, but improves consistency and readability in CI logs.


AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment · ● 626.1K ·

  • expires on Apr 28, 2026, 7:43 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions