ping @tianon PTAL

I was looking for a way to programatically figure out what the "target" branch (VALIDATE_BRANCH) was, but my Git-fu failed me there. I realize you could find it with GitHub's API, but is there a way to figure out using, e.g. some git rev-parse or git branch --points-at magic?

If so, that would ease configuration (i.e., no need to configure these environment variables)

I was looking for a way to programatically figure out what the "target" branch (VALIDATE_BRANCH) was, but my Git-fu failed me there. I realize you could find it with GitHub's API, but is there a way to figure out using, e.g. some git rev-parse or git branch --points-at magic?

Just to proxy some of my thoughts back from our Slack conversation for posterity:

nope, probably not -- which is why we had to do that fetching nonsense in the first place'

GitHub's API is annoying because rate limited

but otherwise it's realllllly annoying to try and get a proper diff of changes against the "target branch" because you can't really know from just Git what the target branch is

the best you can do is guess from common commits, but even that's going to be a bit rubbish

Codecov Report

❗ No coverage uploaded for pull request base (master@44af96c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #38655   +/-   ##
=========================================
  Coverage          ?   36.58%           
=========================================
  Files             ?      610           
  Lines             ?    45217           
  Branches          ?        0           
=========================================
  Hits              ?    16541           
  Misses            ?    26396           
  Partials          ?     2280

@tianon LGTY? 🤗

LGTM