Use spencer's way to debug test failures in ci

get_his_branch_on_your_local.sh

# add his remote
git remote add spalger [email protected]:spalger/kibana.git 
# verbosely fetch his remote branch info
git fetch spalger -v
# bring down the branch he was working on, to your local
git branch --track pr/95667 spalger/pr/95667
# checkout that branch
git checkout pr/95667

I wrote this gist in order to not have to bug spencer the next time I wanna debug something in ci.
I got the idea after viewing his commit log, and seeing these interesting commit msgs:

f947ea57903 (HEAD -> pr/95667, spalger/pr/95667) log rawResponse
dcec35c3f42 run all ciGroup6 tests
1ce7299ce6f log more about bulkCreate method
ee330df9dc8 print options passed to savedObjects.bulkCreate
eb2603af3e5 log in savedObjects.bulkCreate
d79b32b152c stop loading before clean
db92f43c596 only run main functional tests
d1ae018690e 🙃
a0e3e2ddaa1 I have saved approximately -2 hours! yay!
94e529601e1 Merge branch 'master' of github.com:elastic/kibana into pr/95667
4849d6c50f6 another typo
6fb8ce3084d fix typo
42bdfd155e9 allocate a worker
311ea9ecc98 just skip tasks and do just what we need
df4ea986650 only setup one parallel task runner
edbb989decd skip flaky suite (#95642)
8c6163ab826 skip building ts refs when not necessary
2e968784889 disable jest branch
540d4eb4658 isolate test and try to reproduce
92e06b61062 Merge branch 'master' of github.com:elastic/kibana into pr/95667

Now, if I get another ci issue on a test, I can trace through how he did it.
Even if he deletes that branch, I have it on my local for historical use.