Align "Checkout code" step name with standard "Checkout repository" pattern

[Copilot]

Single outlier step name in copilot-setup-steps.yml was inconsistent with the repository-wide convention (233 occurrences of "Checkout repository" vs 1 of "Checkout code").

Changes

• .github/workflows/copilot-setup-steps.yml:18 - Renamed step from "Checkout code" to "Checkout repository"
• .github/workflows/daily-copilot-token-report.lock.yml:318 - Propagated via workflow recompilation

Impact

• Achieves 100% naming consistency across all 152 workflow lock files
• No functional changes - purely cosmetic alignment

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw (http block)
• https://api.github.com/repos/actions/ai-inference/git/ref/tags/v1
  • Triggering command: /usr/bin/gh gh api /repos/actions/ai-inference/git/ref/tags/v1 --jq .object.sha runs/20260217-132652-11056/test-3924446915/.github/workflows /tmp/go-build2517860658/b117/vet.cfg /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet (http block)
• https://api.github.com/repos/actions/checkout/git/ref/tags/v3
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v3 --jq .object.sha husky (http block)
• https://api.github.com/repos/actions/checkout/git/ref/tags/v4
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v4 --jq .object.sha brave.md ../../../**/*.json ache/go/1.25.0/x64/pkg/tool/linu/tmp/gh-aw-git-clone-2219563869 --ignore-path ../../../.prettirev-parse (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v4 --jq .object.sha --write ../../../**/*.json /opt/hostedtoolcache/go/1.25.0/x-nilfunc --ignore-path ../../../.prettirev-parse _TOKEN"; }; f /opt/hostedtoolcache/go/1.25.0/x-tests -uns�� -unreachable=false /tmp/go-build2517860658/b035/vet.cfg 0/x64/bin/node (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v4 --jq .object.sha k/gh-aw/gh-aw/.github/workflows/brave.md config /usr/bin/git remote.origin.urgit ithub/workflows/rev-parse x_amd64/vet git rev-�� --show-toplevel x_amd64/vet /usr/bin/git (http block)
• https://api.github.com/repos/actions/checkout/git/ref/tags/v5
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v5 --jq .object.sha 1009117327/.github/workflows .cfg 64/pkg/tool/linux_amd64/vet (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v5 --jq .object.sha t0 -buildtags (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v5 --jq .object.sha 7860658/b423/_pkg_.a Initial commit 7860658/b423=> template-expressgit (http block)
• https://api.github.com/repos/actions/github-script/git/ref/tags/v8
  • Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha go1.25.0 -c=4 -nolocalimports -importcfg /tmp/go-build2517860658/b383/importcfg -pack /tmp/go-build2517860658/b383/_testmain.go ode_�� (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha json' --ignore-p-c=4 (http block)
• https://api.github.com/repos/actions/setup-go/git/ref/tags/v4
  • Triggering command: /usr/bin/gh gh api /repos/actions/setup-go/git/ref/tags/v4 --jq .object.sha vaScript995558676/001/test-frontmatter-with-env-template-expressions.md ../../../**/*.json /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet --ignore-path ../../../.prettirev-parse (http block)
• https://api.github.com/repos/actions/setup-node/git/ref/tags/v4
  • Triggering command: /usr/bin/gh gh api /repos/actions/setup-node/git/ref/tags/v4 --jq .object.sha /ref/tags/v8 ../../../**/*.json /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet --ignore-path ../../../.prettirev-parse (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/1/artifacts
  • Triggering command: /usr/bin/gh gh run download 1 --dir test-logs/run-1 user.name 64/pkg/tool/linux_amd64/vet (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/12345/artifacts
  • Triggering command: /usr/bin/gh gh run download 12345 --dir test-logs/run-12345 user.email x_amd64/compile son (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/12346/artifacts
  • Triggering command: /usr/bin/gh gh run download 12346 --dir test-logs/run-12346 user.email 64/pkg/tool/linu-test.short=true son (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/2/artifacts
  • Triggering command: /usr/bin/gh gh run download 2 --dir test-logs/run-2 user.name x_amd64/vet (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/3/artifacts
  • Triggering command: /usr/bin/gh gh run download 3 --dir test-logs/run-3 user.name 64/pkg/tool/linux_amd64/vet (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/4/artifacts
  • Triggering command: /usr/bin/gh gh run download 4 --dir test-logs/run-4 user.name x_amd64/compile (http block)
• https://api.github.com/repos/github/gh-aw/actions/runs/5/artifacts
  • Triggering command: /usr/bin/gh gh run download 5 --dir test-logs/run-5 user.name 64/pkg/tool/linu-buildmode=exe (http block)
• https://api.github.com/repos/github/gh-aw/actions/workflows
  • Triggering command: /usr/bin/gh gh workflow list --json name,state,path (http block)
  • Triggering command: /usr/bin/gh gh run list --json databaseId,number,url,status,conclusion,workflowName,createdAt,startedAt,updatedAt,event,headBranch,headSha,displayTitle --workflow nonexistent-workflow-12345 --limit 100 (http block)
  • Triggering command: /usr/bin/gh gh run list --json databaseId,number,url,status,conclusion,workflowName,createdAt,startedAt,updatedAt,event,headBranch,headSha,displayTitle --workflow nonexistent-workflow-12345 --limit 6 (http block)
• https://api.github.com/repos/github/gh-aw/git/ref/tags/v1.0.0
  • Triggering command: /usr/bin/gh gh api /repos/github/gh-aw/git/ref/tags/v1.0.0 --jq .object.sha origin main 64/pkg/tool/linu-nolocalimports (http block)
• https://api.github.com/repos/nonexistent/repo/actions/runs/12345
  • Triggering command: /usr/bin/gh gh run view 12345 --repo nonexistent/repo --json status,conclusion (http block)
• https://api.github.com/repos/owner/repo/actions/workflows
  • Triggering command: /usr/bin/gh gh workflow list --json name,state,path --repo owner/repo 0/x64/bin/sh (http block)
  • Triggering command: /usr/bin/gh gh workflow list --json name,state,path --repo owner/repo ode_modules/.bin-lang=go1.16 (http block)
• https://api.github.com/repos/owner/repo/contents/file.md
  • Triggering command: /tmp/go-build2517860658/b368/cli.test /tmp/go-build2517860658/b368/cli.test -test.testlogfile=/tmp/go-build2517860658/b368/testlog.txt -test.paniconexit0 -test.v=true -test.parallel=4 -test.timeout=10m0s -test.run=^Test -test.short=true (http block)
• https://api.github.com/repos/test-owner/test-repo/actions/secrets
  • Triggering command: /usr/bin/gh gh api /repos/test-owner/test-repo/actions/secrets --jq .secrets[].name (http block)
• https://api.github.com/user
  • Triggering command: /usr/bin/gh gh api user --jq .login (http block)
  • Triggering command: /usr/bin/gh gh api user --jq .login js/**/*.json' ---p (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[step-names] Align "Checkout code" step name with standard "Checkout repository" pattern</issue_title>
<issue_description>## Step Name Alignment Issue

Found during systematic analysis of all 152 workflow lock files (11,743 total steps analyzed).

Summary

The imported workflow configuration file copilot-setup-steps.yml uses "Checkout code" as a step name, which is inconsistent with the overwhelmingly standard pattern of "Checkout repository" used across all other workflows in this repository.

Impact: This inconsistency appears in 1 compiled workflow (daily-copilot-token-report.lock.yml).

Issue Details

Current State

File: .github/workflows/copilot-setup-steps.yml
Line: 18
Current step name: Checkout code

- name: Checkout code
  uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd

Repository-Wide Pattern Analysis

Across all 152 workflow lock files:

• "Checkout repository": 233 occurrences ✅ (standard pattern)
• "Checkout actions folder": 907 occurrences ✅ (specific use case)
• "Checkout PR branch": 153 occurrences ✅ (specific use case)
• "Checkout .github and .agents folders": 152 occurrences ✅ (specific use case)
• "Checkout code": 1 occurrence ❌ (outlier)

Recommended Fix

Change line 18 in .github/workflows/copilot-setup-steps.yml:

- - name: Checkout code
+ - name: Checkout repository
    uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd

Glossary Alignment

This change aligns with the project's established naming conventions identified through pattern analysis:

Pattern: Checkout (target)

• Use "Checkout repository" for main repository checkout
• Use "Checkout (specific-folder)" when checking out specific directories
• Use "Checkout (specific-branch)" when checking out specific branches

Affected Workflows

Only 1 workflow imports this configuration:

• .github/workflows/daily-copilot-token-report.md (imports copilot-setup-steps.yml at line 47)

After fixing the import file and recompiling, the fix will automatically propagate to:

• .github/workflows/daily-copilot-token-report.lock.yml (line 318)

Additional Context

Overall Repository Health: ⭐ Excellent (A- grade)

This is the only critical naming inconsistency found across all workflows. The repository demonstrates outstanding naming conventions with:

• ✅ Consistent use of imperative mood (not gerunds)
• ✅ Proper sentence case capitalization
• ✅ Clear, descriptive names
• ✅ Minimal article usage
• ✅ Well-established patterns for common operations
• ✅ Correct glossary terminology (MCP, GitHub Copilot CLI, safe-outputs)

This single outlier represents just 0.004% of all steps (1 out of 11,743) - an excellent consistency rate of 99.996%.

Agentic Task Description

To implement this fix:

1. Edit the source file: Update .github/workflows/copilot-setup-steps.yml line 18
2. Recompile affected workflows: Run gh aw compile daily-copilot-token-report.md to regenerate the lock file
3. Verify the change: Confirm that daily-copilot-token-report.lock.yml now shows "Checkout repository" at line 318
4. Test the workflow: Ensure the workflow still functions correctly after the change

Related Files

• Import configuration: .github/workflows/copilot-setup-steps.yml:18
• Importing workflow source: .github/workflows/daily-copilot-token-report.md:47
• Compiled workflow: .github/workflows/daily-copilot-token-report.lock.yml:318
• Naming patterns cache: /tmp/gh-aw/cache-memory/step-name-alignment/glossary-analysis.json
• Analysis reports: /tmp/gh-aw/agent/step-name-analysis.txt

Priority

Low Priority - This is a cosmetic consistency improvement with no functional impact. The workflow operates correctly with the current name. However, fixing it achieves perfect naming consistency across all workflows.

---

🤖 AI generated by Step Name Alignment Agent during daily maintenance review on 2026-02-17

Generated by Step Name Alignment

• expires on Feb 19, 2026, 12:34 PM UTC

Comments on the Issue (you are @copilot in this section)

• Fixes [step-names] Align "Checkout code" step name with standard "Checkout repository" pattern #16332

---

💡 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.