tree a91e7e94c664c8b53096469902b254264be88421
parent 5c5a6a349b20e1fd07784e0f07251ea8b6b8d1ec
author Robert Houghton <rhoughton@pivotal.io> 1571777659 -0700
committer GitHub <noreply@github.com> 1571777659 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdr2x7CRBK7hj4Ov3rIwAAdHIIAFNpucFrlawgGc74v2kFuRw0
 2eE8F8A+PErO4i1nRUpMJHzYzaSbuoFkS0IB1u6xVO+t4/z1zVgOe7dFoOQ3bfvo
 u8Ov3/gIMjlgUpaoqWM8bVMYS+2UE57MHQQUfDw/A/Aky4CyicA7MyrDbl7AhOCJ
 kNFWZcruUxw0/02pTRAp7ur0rFbHTSrd3XZtl3kMJxLn7JUZ8DnOwdSK04sbCYBm
 QkNjDQUPCeYmBTr+KD+c4HuTUXiO2X8GJO+DzsvUeeUjnh2sbOSBM7D7yX9QD1lV
 R1dgRMh5LMSpwzLPonzMzePl8LJc+mc9I5CkGYioKg7UWMevZnHo2aiVG672YVI=
 =AS+8
 -----END PGP SIGNATURE-----
 

GEODE-7281: UpdatePassingTokens only moves git sha forward. (#4134)

* GEODE-7281: UpdatePassingTokens only moves git sha forward.

Use `git merge-base --is-ancestor <old> <new>` to check that the SHA we
publish as 'passing' is moving forward in git history.

* force git behavior in attach-sha-to-branch