It is generally a good practice to embed the information of the tracking tool inside the git commit message so finding this information is straight forward, and you can jump from any commit to the GitHub issue also instaneously.
We use Gerrit with a "tracked-on" field on the last paragraph of the commit message (which is supported by gerrit) in order to link this commit to our tracking tool. Github seems to support only "#123" substring in the commit message. Beware because it will close automatically the issue if the string "Fix #123" is found in the first line, and a single commit can refer to more than only one github issue. My 2 cents, ----- Gaetan 2014-02-17 23:43 GMT+01:00 Palmer Cox <[email protected]>: > 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 <[email protected]> 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 >> [email protected] >> https://mail.mozilla.org/listinfo/rust-dev >> >> > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
