Adding go-gerrit - Go cient library for Gerrit Code Review

[andygrunwald]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/andygrunwald/go-gerrit
• pkg.go.dev: https://pkg.go.dev/github.com/andygrunwald/go-gerrit
• goreportcard.com: https://goreportcard.com/report/github.com/andygrunwald/go-gerrit
• coverage service link (codecov, coveralls, etc.):

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

[github-actions]

Thank you for contributing to awesome-go. We will review your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• repo link
• pkg.go.dev
• goreportcard.com
• coverage

Your project is under review. It may take a few days to be approved.

[yassinebenaid]

Test coverage is missing !!

[andygrunwald]

@yassinebenaid I don't have a codecov or coveralls integration. I do not plan to integrate this into go-gerrit.
The testing coverage of this library is currently:

$ go test -coverprofile=.coverage.html -coverpkg=.

PASS
coverage: 28.8% of statements in .
ok  	github.com/andygrunwald/go-gerrit	0.698s

This library has its fair share of use in bigger projects like:

• k8s/prow: https://github.com/kubernetes-sigs/prow/blob/f945d434db09ce0e4e7d6f9c69ac4b6a8cf59191/go.mod#L12
• ovh/cds: https://github.com/ovh/cds/blob/master/go.mod#L14
• wtf: https://github.com/wtfutil/wtf/blob/master/go.mod#L13
• zoekt (sourcegraph): https://github.com/sourcegraph/zoekt/blob/7caa174ced8267dd8782488c2701f56145c74cfa/go.mod#L7

[yassinebenaid]

Fair enough. thanks for clarification.