Skip to content
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.

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

Go Lint fixes and GitHub actions added for Test, Coverage and Golint #27

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

Chetan177
Copy link

Changes:

  • Go Lint fix for the following:
constants/error_code.go:4:2: don't use ALL_CAPS in Go names; use CamelCase
constants/error_code.go:4:2: exported const BAD_REQUEST_ERROR should have comment (or a comment on this block) or be unexported
constants/error_code.go:5:2: don't use ALL_CAPS in Go names; use CamelCase
constants/error_code.go:6:2: don't use ALL_CAPS in Go names; use CamelCase
constants/http_status_code.go:7:2: don't use ALL_CAPS in Go names; use CamelCase
constants/http_status_code.go:9:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:5:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:7:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:9:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:11:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:13:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:15:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:17:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:19:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:21:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:23:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:25:2: don't use ALL_CAPS in Go names; use CamelCase
constants/url.go:27:2: don't use ALL_CAPS in Go names; use CamelCase
  • Added Test, Coverage, Lint check using Git Action instead of TravisCI Add CI #11

@Chetan177 Chetan177 changed the title Go Lint fixes and GitHub actions added for Test, Coverage and Goling Go Lint fixes and GitHub actions added for Test, Coverage and Golint Apr 17, 2021
@Chetan177
Copy link
Author

Please let me know if code coverage through codecov.io is required.

It will show code coverage on codecov.io like this:
image

And will also add a comment on the related PR like this:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant