Fix GitHub Actions build pipeline failures

[Copilot]

The GitHub Actions build pipeline was failing due to a critical step ordering issue and several outdated configurations.

Problem

The build was failing with the error:

go: go.mod file not found in current directory or any parent directory.
'go get' is no longer supported outside a module.

This occurred because the linter installation step was running before the code checkout step, so go get was trying to install packages without access to the project's go.mod file.

Solution

Fixed multiple issues in the build pipeline:

1. Reordered workflow steps: Moved code checkout before linter installation so go.mod is available
2. Modernized package management:
   • Replaced deprecated go get -u github.com/mgechev/revive with go install github.com/mgechev/revive@latest
   • Replaced deprecated go get -v -t -d ./... with go mod tidy
3. Updated action versions: Upgraded from v2 to v4 for both setup-go and checkout actions
4. Fixed Go version compatibility: Updated from ^1.17 to ^1.23 to match the go.mod requirements
5. Ensured binary accessibility: Used full path $(go env GOPATH)/bin/revive for reliable linter execution

Testing

All build steps now pass successfully:

• ✅ Dependencies download correctly
• ✅ Linting completes without errors
• ✅ go vet passes
• ✅ All tests pass
• ✅ Package builds successfully

The build pipeline is now modernized and ready for reliable CI/CD operations.

---

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