Make bors warn about commits without issue #s

[brson]

As @brson says below: Let's run an adapted http://github.com/jdm/highfive under bors's account.

(Original bug follows)

---

Original title: Make bors warn about commits without issue #s

In the meeting today we decided to start trying to get more issue #s on pull requests so it's more clear why things are changing.

[pnkfelix]

To be clear: Issue #'s on pull requests and individual commits. The latter is important e.g. for users of git blame.

(I'll put a link to the meeting notes in the description so people can see the discussion on this topic.)

[pnkfelix]

(also here is the bors bug I mentioned in the meeting: graydon/bors#20 )

[brson]

I'm thinking we may not want to conflate bors' duties. Right now she doesn't do any sort of linting, and her stateless design sometimes makes this kind of thing hard. Servo has a dedicated 'highfive' bot for this purpose.

[brson]

Let's run an adapted http://github.com/jdm/highfive under bors's account.

[pnkfelix]

@brson so we should close this then, right? Or do you want to just repurpose this ticket? (In which case I can revise the title+description.)

[nrc]

cc me

@pnkfelix fwiw I'd just re-purpose this bug

[pnkfelix]

@nick29581 yeah okay. Revised.

[nrc]

highfive is working for Rust now. Not doing the fancy issue number checking though

[steveklabnik]

I'm marking this as 'lint,' even though that's a bit odd. Is this still something we want?

[nrc]

It's not really a lint thing - we wouldn't lint for it, we would check using highfive. However, GH seems to be better at getting links to issues from commits and I haven't noticed this problem so much recently. Also, seems like changing the culture to have issues filed for every bug fix would be impossible. Closing.