hjimmy/tg-origin: source/pkg/template/controller/readiness.go; 5 LoC

Found a possible issue in [hjimmy/tg-origin](https://www.github.com/hjimmy/tg-origin) at [source/pkg/template/controller/readiness.go](https://github.com/hjimmy/tg-origin/blob/07e45cb8ec631f158f6c7c29330a9cdeae9f4a29/source/pkg/template/controller/readiness.go#L72-L76)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/hjimmy/tg-origin/blob/07e45cb8ec631f158f6c7c29330a9cdeae9f4a29/source/pkg/template/controller/readiness.go#L72-L76)

Click here to show the 5 line(s) of Go which triggered the analyzer.

```go
for _, item := range builds.Items {
if item.Annotations[buildutil.BuildNumberAnnotation] == strconv.FormatInt(bc.Status.LastVersion, 10) {
return checkBuildReadiness(&item)
}
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {checkBuildReadiness 1} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 07e45cb8ec631f158f6c7c29330a9cdeae9f4a29

Read source/pkg/template/controller/readiness.go around lines 72-76 and inspect checkBuildReadiness, then determine whether passing the range-loop item address is a bug, mitigated, or desirable behavior. The issue's stated completion condition is to classify the finding with the corresponding reaction; no code change or test is specified.

Written by the indexing model from the issue text.