Skip to content

Add submodule checkout to copilot-setup-steps.yml #64761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wtgodbe merged 1 commit into from
Dec 13, 2025
+2 −0
Merged

Add submodule checkout to copilot-setup-steps.yml #64761

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/copilot-setup-steps.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ jobs:
# If you do not check out your code, Copilot will do this for you.
steps:
- uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v4.2.2
with:
submodules: 'true'
Copy link

Copilot AI Dec 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The submodules parameter should be a boolean value 'true' or 'false', or a string specifying the checkout strategy ('recursive'). While the string 'true' will work, it's more idiomatic in GitHub Actions to use the boolean true without quotes, or use 'recursive' to explicitly check out all nested submodules. Looking at other workflows in the repository (e.g., validate-npm-package-lock-json.yml uses submodules: false), the convention is to use boolean values without quotes.

Suggested change
submodules: 'true'
submodules: true

Copilot uses AI. Check for mistakes.

# Include PrepareForHelix to maximise what is downloaded here
- name: Build solution
Expand Down