Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.95%. Comparing base (2b8c7fa) to head (2328ae7).
Report is 105 commits behind head on master.

@@            Coverage Diff             @@
##           master    #3254      +/-   ##
==========================================
- Coverage   97.72%   92.95%   -4.77%     
==========================================
  Files         153      171      +18     
  Lines       13390    11680    -1710     
==========================================
- Hits        13085    10857    -2228     
- Misses        215      729     +514     
- Partials       90       94       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Thank you, @air-hand, this is looking great! Just a couple minor nits to address, please, then we will be ready for a second LGTM+Approval from any other contributor to this repo before merging.

@gmlewis
Thanks for the review!
I have applied your suggestions.

Hello, @gmlewis.

I am waiting for a second LGTM+ approval from other contributors to this repository before merging it.

I know this repository is supported by volunteers, but I want to release this.
If possible, could you please tell me how to find a second reviewer as PR author? 🙏

If possible, could you please tell me how to find a second reviewer as PR author?

Do you have a coworker you could ask to perform the code review?

Do you have a colleague you can ask to review code?

Probably not.
I think that PR reviewers for this repository must be contributors, cause I can't assign myself as a reviewer other PR just now.

I think that PR reviewers for this repository must be contributors, cause I can't assign myself as a reviewer other PR just now.

We welcome new contributors to this repo all the time. All new Go developers are welcome to contribute with PRs or code reviews. See CONTRIBUTING.md for more information.

Oh, I mean that a user who has never committed to the default branch (i.e., a user who is not listed as a "contributor") may not be able to assign itself as a reviewer on github because I have tried other PR but I couldn't.

I've asked @srgustafson8 if a code review might be possible since @srgustafson8 is actively working on other PRs right now...

Oh, I mean that a user who has never committed to the default branch (i.e., a user who is not listed as a "contributor") may not be able to assign itself as a reviewer on github because I have tried other PR but I couldn't.

Just FYI - it is almost never necessary that a reviewer be assigned in this repo on any particular PR.
We welcome all code reviews and rarely ever assign specific reviewers.

In fact, @air-hand - please feel free to perform code reviews yourself on any open PRs that have the "Needs Review" label... all contributions are greatly appreciated!

Just FYI - it is almost never necessary that a reviewer be assigned in this repo on any particular PR.

Thanks @gmlewis, I finally understand. (I had always assign reviewer myself on PR before code review...)

Thanks @gmlewis, I finally understand. (I had always assign reviewer myself on PR before code review...)

Yes, that is totally reasonable and quite common especially in a corporate environment.
No worries at all. Thanks again for all your help to make this repo better! It is greatly appreciated.

@air-hand @gmlewis will try and get to this one today :)

Thank you, @srgustafson8 !
Merging.