Fix workflow-lint job by provisioning Go before actionlint

[Copilot]

GitHub Actions workflow lint was failing in run 33597126021 (job 100142779142) because the runner executed go run ...actionlint... without Go installed. This change makes the lint job self-sufficient across runners that do not prebundle Go.

• Root cause

  • workflow-lint invoked:
    • go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.12 .github/workflows/*.yml
  • but had no prior Go toolchain setup step.

• Workflow change

  • Added actions/setup-go in .github/workflows/ci.yml before Run actionlint.
  • Pinned action SHA and configured:
    • go-version: stable

• Resulting job shape

  - name: Set up Go
    uses: actions/setup-go@924ae3a1cded613372ab5595356fb5720e22ba16 # v6.5.0
    with:
      go-version: stable
  
  - name: Run actionlint
    run: go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.12 .github/workflows/*.yml

[Copilot]

🟢 Approval recommended

The single-step CI addition is correct, the pinned action SHA matches its verified v6.5.0 tag, and it properly resolves the missing Go toolchain that caused the lint job to fail.

Pull request overview

This PR fixes the failing workflow-lint CI job by provisioning the Go toolchain before running actionlint. The job invokes go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.12 but had no prior Go setup step, so it failed on runners that do not prebundle Go. Adding actions/setup-go restores the job's self-sufficiency.

Changes:

• Added a Set up Go step using actions/setup-go (pinned to SHA 924ae3a1cded613372ab5595356fb5720e22ba16, v6.5.0) with go-version: stable.
• Placed the new step immediately before the Run actionlint step so the toolchain is available at runtime.

File summaries

File	Description
.github/workflows/ci.yml	Adds an actions/setup-go step before Run actionlint so the go run invocation has a Go toolchain available.

I verified that the pinned SHA 924ae3a1cded613372ab5595356fb5720e22ba16 matches the v6.5.0 tag of actions/setup-go exactly, that the version comment is accurate, that go-version: stable is a supported value, and that the new step is correctly ordered before actionlint and consistently indented with the surrounding steps. No issues found.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.