feat: adding golint and a Makefile

[mfreeman451]

1. Added a Makefile that includes tests for golint, ineffassign, gosec, gocov, etc.
2. Adding coverage.yml to ci for gocov
3. Added golintci-lint.yml to ci for golint
4. Updated a test so it would pass gosec check

[nekomeowww]

Is there any better workaround or solution to such feature? I don't think it is elegant and proper to commit the README.md changes within CI/CD scope and interfere the branch that the developers working on, especially when we are doing some traditional GitFlow actions (such as rebase the upstream branch or so).

What do you think @tmc ?
If we are surely use such method to update the badges, I suggest to add a concurrency config in GitHub Actions workflow file to prevent conflicts, you can read more here: https://docs.github.com/en/actions/using-jobs/using-concurrency

[nekomeowww]

Or how about we make two workflow definitions:

• Pull Request into main, focusing on testing and report the developers
• Push into main, focusing on updating the test coverages badges

[tmc]

I really like what I'm seeing here, thanks for reviewing @nekomeowww -- good input.

[nekomeowww]

There are some conflicts. Remember to get your branch updated 😉

[rdbell]

Looking forward to a more uniform codebase with conventions to follow. Let's get this in.

[nekomeowww]

Every file should ends with a empty new line.

Suggested change

	branch: ${{ github.head_ref }}
	branch: ${{ github.head_ref }}

You can ask IDE/editors perform such actions automatically, if you are using Visual Studio Code, you could add one line that enable this feature easily:

{
  "files.insertFinalNewline": true,
}

[nekomeowww]

Could you please format the new lines of end of the file?

Suggested change

[tmc]

I believe this is obviated by #42