imply bitten_apple -> food_bite

BUR #5575 has been approved by @evazion.

create implication bitten_apple -> food_bite

A biten apple has food bite on it.

The bulk update request #5575 (forum #186580) has been approved by @evazion.

These tags should be made consistent with each other. Either apple bite or bitten food.

BUR #5588 has been rejected.

create alias food_bite -> bite_hole
create alias bitten_food -> bite_hole

I've come to realise that food_bite may not have been the best name for it. When I created this tag I figured using food in the name might help people find it in the autocomplete, but in reality it gets drowned out by other food_* tags. It's also actually just for the hole left by a bite, and since it's not limited to food, bitten_food is a no-go - if (for whatever reason) someone were to take a bit out of a brick, that wouldn't count as bitten_food despite fitting the theme of the tag.

I suggest aliasing it to bite_hole. The new name is consistent with bite_mark, and both tags are applicable regardless of what's being bitten. I've also included a utility alias for bitten_food since an overwhelming majority of these posts do feature food with a bite taken out of it.

This bulk update request is pending automatic rejection in 5 days.

bite hole sounds like a terrible name and makes me think of anything but food.

This bulk update request has been rejected because it was not approved within 60 days.

The bulk update request #5588 (forum #186697) has been rejected by @DanbooruBot.