Running jest --changedSince=blablabla (as long as blablabla is _not_ a branch/tag/commit (anything that's not a valid reference)) crashes with an unhandled rejection.
Steps to reproduce the behavior:
jest --changedSince=some-bad-revision
A clean error saying that the reference was impossible to resolve, or something. Probably just show the error from git is best
N/A, can be reproduced in any repo with VCS (including the jest repo itself).
npx envinfo --preset jestPaste the results here:
Environment:
OS: macOS High Sierra 10.13.6
Node: 8.11.1
Yarn: 1.9.4
npm: 6.4.1
Watchman: 4.9.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: EAP AI-145.3111935 AI-145.3111935
Is it ok if I try my hands on this?
@Keraito go for it!
@Keraito are you still working on this? Mind if I take a look?
For whoever is picking this issue up, Id recommend handling both scenarios where a user uses git and when a user uses mercurial.
Sorry @SimenB @rogeliog, suddenly couldn't quite find the time to work on this, so @khuyn003 go ahead.
When running command npm test -- --changedSince refs/heads/develop I got
(node:29084) UnhandledPromiseRejectionWarning: 128: fatal: bad revision '^refs/heads/develop'
Is the string refs/heads/develop invalid branch reference?
Please open up a separate issue with reproduction steps