git_ref ... branch, tag, or hash?

I've had a few 'Webhook for OTHER branch Received! Ignoring" warnings in my logs...

It turns out that h_git prefers a tag over a branch these days to store as git_ref.
Maybe intentional, but I'm trying to figure out the best resolution.

I have a few platforms that I'd like to keep on a branch. After every release this tip of this branch has a tag .... When that platform is then verified it stores the git tag in the git_ref field.

So after the release the git pull webhook is failing because the platform is now on the tag which it considers an 'OTHER branch'.

We could try to amend the code in drush/provision_git.drush.inc:_provision_git_update_git_meta_data() or change the check in the webhook code.

Or maybe we need to start storing two values? One for a branch, the other for a tag ... or even commit hash?