CodeLingo Bot

Use [CodeLingo](https://codelingo.io) to automatically fix function comments following the [Code Review Comments guidelines](https://github.com/golang/go/wiki/CodeReviewComments#error-strings). This patch was generated by running the CodeLingo Rewrite Flow over the "[go-error-fmt](https://github.com/codelingo/codelingo/blob/master/tenets/codelingo/code-review-comments/go-error-fmt/codelingo.yaml)" Tenet. Note: the same...

Fix function comments based on best practices from Effective Go

1

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

Fix function comments based on best practices from Effective Go

1

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

Fix function comments based on best practices from Effective Go

2

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

Fix function comments based on best practices from Effective Go

1

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

Fix function comments based on best practices from Effective Go

2

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

Fix function comments based on best practices from Effective Go

1

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

Fix function comments based on best practices from Effective Go

2

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From [effective go](https://golang.org/doc/effective_go.html#commentary). PR generated...

It looks like this is a Go project. This pull request will add a codelingo.yaml file with some common Go Tenets that CodeLingo will use to review Pull Requests to...

Fix comments according to best practices by Effective Go

1

Use [CodeLingo](https://codelingo.io) to automatically fix function comments following the [Effective Go guidelines](https://golang.org/doc/effective_go.html#commentary) in [CONTRIBUTING.md](https://github.com/northwesternmutual/kanali/blob/master/CONTRIBUTING.md). This patch was generated by running the CodeLingo Rewrite Flow over the "[comment-first-word-as-subject](https://github.com/codelingo/codelingo/blob/master/tenets/codelingo/effective-go/comment-first-word-as-subject/codelingo.yaml)" Tenet. Note: the...