wercker/triage: issue.go; 8 LoC

Found a possible issue in [wercker/triage](https://www.github.com/wercker/triage) at [issue.go](https://github.com/wercker/triage/blob/35e5f8357c96b243a506a47aaeaccc3b0f0ee458/issue.go#L95-L102)

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.

> reference to p was used in a composite literal at line 98

[Click here to see the code in its original context.](https://github.com/wercker/triage/blob/35e5f8357c96b243a506a47aaeaccc3b0f0ee458/issue.go#L95-L102)

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

```go
for i, p := range ps {
for _, l := range issue.Labels {
if p.Name == *l.Name {
issuePriority = IssuePriority{Index: i + 1, Priority: &p}
break
}
}
}

```

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: 35e5f8357c96b243a506a47aaeaccc3b0f0ee458