Skip to content

[step-names] Align compiler-generated step name: "copilot" → "Copilot" #13814

@github-actions

Description

@github-actions

Step Name Alignment Issue

Found during automated step name analysis across all workflow lock files.

Summary

The compiler generates a step name with lowercase "copilot" which doesn't align with the project glossary that consistently uses "Copilot" (capitalized) or "GitHub Copilot CLI" for the full product name.

Issue Identified

Inconsistent capitalization: "copilot" → "Copilot"

Current step name:

  • "Assign copilot to created issues" (lowercase - incorrect)

Issue:
The project glossary and established patterns use "Copilot" (capitalized) when referring to GitHub Copilot. Other step names correctly use:

  • "Install GitHub Copilot CLI" ✓
  • "Execute GitHub Copilot CLI" ✓
  • "Copy Copilot session state files" ✓
  • "Fetch Copilot PR data" ✓
  • "Fetch Copilot session data" ✓
  • "Validate COPILOT_GITHUB_TOKEN secret" ✓

Suggested improvement:

  • "Assign copilot to created issues" → "Assign Copilot to created issues"

Glossary reference: The glossary consistently refers to "GitHub Copilot" or "Copilot" (capitalized), never lowercase "copilot".

Source Locations

This step name is generated by the compiler in two locations:

  1. pkg/workflow/compiler_safe_outputs_job.go:239

    steps = append(steps, "      - name: Assign copilot to created issues\n")
  2. pkg/workflow/create_issue.go:125

    steps = append(steps, "      - name: Assign copilot to created issues\n")

Impact

Workflows affected: 2 compiled workflows

  • .github/workflows/breaking-change-checker.lock.yml (line 1175)
  • .github/workflows/duplicate-code-detector.lock.yml (line 1059)

Priority: Medium - This is a consistency and branding issue. The functionality is correct, but the naming doesn't follow the project's terminology standards.

Agentic Task Description

To fix this issue:

  1. Update compiler code - Change both instances in the Go source files:

    • In pkg/workflow/compiler_safe_outputs_job.go:239
    • In pkg/workflow/create_issue.go:125
    • Change: "Assign copilot to created issues""Assign Copilot to created issues"
  2. Recompile affected workflows - Run compilation to regenerate the .lock.yml files:

    gh aw compile breaking-change-checker.md
    gh aw compile duplicate-code-detector.md
  3. Verify the fix - Confirm the step names are updated in the lock files:

    grep -n "Assign Copilot to created issues" .github/workflows/*.lock.yml
  4. Update tests if needed - Check if any tests reference the old step name:

    • pkg/workflow/compile_outputs_issue_test.go:349 references this step name in tests

Context: Overall Step Name Quality

This issue was found during a comprehensive analysis of all 213 unique step names across 143 workflow lock files. The good news:

Excellent consistency overall! All major patterns are consistent:

  • Setup (component) (21 instances)
  • Install (tool) (20 instances)
  • Download (artifact) (17 instances)
  • Upload (artifact) (18 instances)
  • Create (resource) (10 instances)

Correct imperative mood throughout - No "Installing", "Downloading", etc.

Proper MCP terminology - All instances correctly use "MCP" (capitalized)

Correct Safe Outputs/Safe Inputs usage - Properly using title case in step names

This is the only inconsistency found that doesn't align with the glossary.

Related Files

  • Compiler source: pkg/workflow/compiler_safe_outputs_job.go, pkg/workflow/create_issue.go
  • Test file: pkg/workflow/compile_outputs_issue_test.go
  • Affected workflows: breaking-change-checker.lock.yml, duplicate-code-detector.lock.yml
  • Project glossary: docs/src/content/docs/reference/glossary.md

AI generated by Step Name Alignment for daily maintenance

AI generated by Step Name Alignment

  • expires on Feb 6, 2026, 11:57 PM UTC

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions