Closed zakir-code closed 3 days ago
This pull request introduces a new job called custom-lint
in the GitHub Actions workflow for a Go project, which executes a linter script. The lint
job is updated to depend on this new job instead of the removed check-no-lint
step. The Makefile
reflects these changes with the addition of the custom-lint
target. Furthermore, several method renamings occur in the test files to standardize the naming convention, particularly regarding cross-chain functionality, without altering their logic or control flow.
File | Change Summary |
---|---|
.github/workflows/golang.yml | Added new job custom-lint . Modified lint job by removing check-no-lint step. |
Makefile | Added target custom-lint , removed check-no-lint , and updated lint to depend on custom-lint . |
scripts/linter.sh | New script added for enforcing pattern suppression limits in Go codebases. |
tests/crosschain_test.go | Renamed method CrossChainTest to CrosschainTest . |
tests/integration_test.go | Renamed method CrossChainTest to CrosschainTest and GetCrossChainByName to GetByName . |
tests/precompile_suite.go | Renamed methods TransferCrossChain to TransferCrosschain and CrossChainAndResponse to CrosschainAndResponse . |
custom-lint
job, focusing on improving code quality and consistency in linting practices.🐇 In the land of code so bright,
A linter hops, a joyful sight.
With patterns checked and names made right,
Our project shines, a pure delight!
Custom linting, oh what a cheer,
In every file, we hold you dear!
🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Summary by CodeRabbit
Release Notes
New Features
custom-lint
) in the GitHub Actions workflow for improved code quality checks.linter.sh
) to enforce pattern suppression limits in Go codebases.Bug Fixes
Chores
custom-lint
target.