romanornr/reeetipbot-public: bots/telegram.go; 10 LoC

Found a possible issue in [romanornr/reeetipbot-public](https://www.github.com/romanornr/reeetipbot-public) at [bots/telegram.go](https://github.com/romanornr/reeetipbot-public/blob/476d922b3eadf1328eacdfc10c8a2b02714531ef/bots/telegram.go#L55-L64)

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/romanornr/reeetipbot-public/blob/476d922b3eadf1328eacdfc10c8a2b02714531ef/bots/telegram.go#L55-L64)

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

```go
for update := range updates {
if update.Message == nil { // ignore any non-Message Updates
continue
}

msg := tgbotapi.NewMessage(update.Message.Chat.ID, update.Message.Text)

command := telegram.commandParser(msg.Text, update)
telegram.handler(command, &update)
}

```

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 {handler 2} 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: 476d922b3eadf1328eacdfc10c8a2b02714531ef

Open bots/telegram.go at lines 55-64 for commit 476d922b3eadf1328eacdfc10c8a2b02714531ef and review the range-loop pointer use. Read the linked classification descriptions, decide whether this is a Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction on issue #17066.

Written by the indexing model from the issue text.