Align step names in release, super-linter, and mergefest workflows#10406
Closed
Align step names in release, super-linter, and mergefest workflows#10406
Conversation
- Change "Checkout" to "Checkout repository" in release.md (2 instances) - Change "Checkout Code" to "Checkout repository" in super-linter.md - Change "Setup git configuration" to "Setup Git configuration" in mergefest.md - Recompile affected workflow lock files Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Align step names in workflow lock files
Align step names in release, super-linter, and mergefest workflows
Jan 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three workflow files contained step names that deviated from established patterns: generic "Checkout" without target specification, "Checkout Code" using non-standard terminology, and "Setup git configuration" with lowercase "git".
Changes
Checkout→Checkout repository(2 instances)Checkout Code→Checkout repositorySetup git configuration→Setup Git configurationPattern compliance
Checkout <target>convention (used 952× across codebase: "repository", "actions folder", "PR branch")Configure Git credentials(193 instances)Original prompt
This section details on the original issue you should resolve
<issue_title>[step-names] Align step names in release.lock.yml, super-linter.lock.yml, and mergefest.lock.yml</issue_title>
<issue_description>Found in:
.github/workflows/release.lock.yml,.github/workflows/super-linter.lock.yml,.github/workflows/mergefest.lock.ymlSummary
Analysis of all 126 workflow lock files identified 3 step names with minor inconsistencies that should be aligned with established naming patterns. These are low-impact issues but fixing them will improve consistency across the codebase.
Issues Identified
1. [Medium Priority] Generic "Checkout" Step Name
Current step names:
.github/workflows/release.lock.yml:973- "Checkout".github/workflows/release.lock.yml:1352- "Checkout"Issue:
These steps use the generic name "Checkout" which doesn't follow the established pattern
Checkout <target>. The established pattern is used 758 times for "Checkout actions folder" and 194 times for "Checkout repository".Suggested improvement:
Pattern reference: The established pattern is
Checkout <target>to provide clarity about what is being checked out.2. [Medium Priority] "Checkout Code" Naming
Current step name:
.github/workflows/super-linter.lock.yml:1235- "Checkout Code"Issue:
Uses "Code" as the target, which is less specific than the standard "repository". All other checkout steps use either "Checkout repository" (194 instances), "Checkout actions folder" (758 instances), or "Checkout PR branch" (124 instances).
Suggested improvement:
Pattern reference: The established pattern uses specific, consistent target names: "repository", "actions folder", "PR branch".
3. [Medium Priority] Lowercase "git" in Setup Pattern
Current step name:
.github/workflows/mergefest.lock.yml:127- "Setup git configuration"Issue:
Uses lowercase "git" which is inconsistent with other Setup patterns that capitalize proper nouns. Examples of correct capitalization:
Suggested improvement:
Glossary reference: While not explicitly in the glossary, "Git" is a proper noun (the version control system) and should be capitalized consistently, as demonstrated by the 193 instances of "Configure Git credentials".
Positive Findings
The previous run on 2026-01-15 identified 4 instances of non-hyphenated "cache memory" and "repo memory" that violated the glossary. These have all been fixed! ✅
All current instances now correctly use:
This demonstrates that the step name alignment process is working well.
Additional positive findings:
Agentic Task Description
To fix these step names:
Update source workflow files (
.mdfiles, not.lock.yml):.github/workflows/release.md- Change two "Checkout" steps to "Checkout repository".github/workflows/super-linter.md- Change "Checkout Code" to "Checkout repository".github/workflows/mergefest.md- Change "Setup git configuration" to "Setup Git configuration"Recompile workflows - Run
gh aw compileon the affected workflows to regenerate.lock.ymlfilesVerify changes - Confirm the step names in the
.lock.ymlfiles match the expected namesTest workflows - Ensure workflows still function correctly after the changes
Related Files
.github/workflows/release.md,.github/workflows/super-linter.md,.github/workflows/mergefest.md.github/workflows/release.lock.yml,.github/workflows/super-linter.lock.yml,.github/workflows/mergefest.lock.ymldocs/src/content/docs/reference/glossary.md/tmp/gh-aw/cache-memory/step-name-alignment/naming-conventions.mdPriority
This issue is Medium Priority - these are minor inconsistencies that don't affect functionality but should be fixed to maintain consistency acros...
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.