You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 18, 2026. It is now read-only.
In the release workflow's test job, the actions/setup-go step appears twice (lines 90-95 and lines 121-126) with identical configuration. The second invocation is redundant since Go is already set up from the first step.
Location
.github/workflows/release.yml, test job:
First setup (line 90-95): Sets up Go before running tests
Second setup (line 121-126): Sets up Go again before cross-platform builds
Both steps use the exact same action, version, and parameters.
Impact
Adds unnecessary execution time to each release workflow run
Creates maintenance burden (two places to update if Go setup changes)
May confuse contributors reading the workflow
Suggested Fix
Remove the second Set up Go step (lines 121-126). The Go toolchain persists across steps within the same job.
Problem
In the release workflow's
testjob, theactions/setup-gostep appears twice (lines 90-95 and lines 121-126) with identical configuration. The second invocation is redundant since Go is already set up from the first step.Location
.github/workflows/release.yml,testjob:Both steps use the exact same action, version, and parameters.
Impact
Suggested Fix
Remove the second
Set up Gostep (lines 121-126). The Go toolchain persists across steps within the same job.