github: What to do when unittests fail?

Andrej Mitrovic andrej.mitrovich at gmail.com
Tue May 24 05:57:37 PDT 2011


On 5/24/11, David Nadlinger <see at klickverbot.at> wrote:
> master, then create a feature branch for your pull request (»git
> checkout -b spiffy-new-feature«).

Ok, but what about the errors in my original post? I should make sure
all unittests pass when I make a pull request, right?

If that's required I think I'd have to first checkout an older commit.
But I'm not sure which one. There's a bunch of them for dates May 16th
and older listed here:
http://d.puremagic.com/test-results/platform-history.ghtml?os=Win_32

E.g. this one: http://d.puremagic.com/test-results/test_data.ghtml?dataid=62436
It says:
>From git://github.com/D-Programming-Language/phobos
   3b628ae..d1d8124  master     -> origin/master

I'm not sure what 3b628ae..d1d8124 means, should I do "git checkout
d1d8124" or something similar to get this commit?


More information about the Digitalmars-d-learn mailing list