laszlocph/woodpecker: remote/bitbucket/parse.go; 6 LoC

Found a possible issue in [laszlocph/woodpecker](https://www.github.com/laszlocph/woodpecker) at [remote/bitbucket/parse.go](https://github.com/laszlocph/woodpecker/blob/0cf4554ea0eb961c0b70662be64ce153664d51c0/remote/bitbucket/parse.go#L64-L69)

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/laszlocph/woodpecker/blob/0cf4554ea0eb961c0b70662be64ce153664d51c0/remote/bitbucket/parse.go#L64-L69)

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

```go
for _, change := range hook.Push.Changes {
if change.New.Target.Hash == "" {
continue
}
return convertRepo(&hook.Repo), convertPushHook(&hook, &change), nil
}

```

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 {convertPushHook 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: 0cf4554ea0eb961c0b70662be64ce153664d51c0

Inspect remote/bitbucket/parse.go at lines 64-69 and read the analyzer output alongside the range-loop handling. Determine whether the change pointer can escape or be passed unsafely, then classify the finding as Bug, Mitigated, or Desirable Behavior using the requested reaction.

Written by the indexing model from the issue text.