I believe that bors never does a fast forward merge and that the merge commits always contain the pull number. So, if you have a particular commit and you want to find the issue that it was part of, I believe you can always look look through its children until you find a commit by "bors" which should have a commit message like: "auto merge of #12313 : bjz/rust/tuple, r=huonw" which contains the issue number.
Let says that the commit you are interested in is "6f39eb1". I think if you run the command: git log --author "bors" --ancestry-path 6f39eb1..origin/master And look at the commit at the very bottom of the list, that will be the merge commit that you are interested in. I'm not a git expert - there may be a better way to do that. -Palmer Cox On Mon, Feb 17, 2014 at 4:50 PM, Nick Cameron <n...@ncameron.org> wrote: > How would people feel about a requirement for all commit messages to have > an issue number in them? And could we make bors enforce that? > > The reason is that GitHub is very bad at being able to trace back a commit > to the issue it fixes (sometimes it manages, but not always). Not being > able to find the discussion around a commit is extremely annoying. > > Cheers, Nick > > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
