Ran into one of these when debugging an action workflow a while ago. Locally, all the tests would pass, but the tests kept failing on GitHub. Diving into the l

Ran into one of these when debugging an action workflow a while ago. Locally, all the tests would pass, but the tests kept failing on GitHub. Diving into the logs, the SHA that the tests were run against was not the commit we were testing locally, but the "merge candidate" that had apparently auto merged some lines of code that resulted in a syntax error. Looking back, it makes perfect sense that _that_ is what tests are run against, but I had never realized that before (and the platform definitely hides it from you). Before we moved to GitHub actions, we were just running tests against the head of a feature branch.