i didn't ask you to, you don't work for me whoever is in charge of policy there is wrong, if the project is intended to be open source open source is social, that's a huge key difference to closed source
also, tags are there for some use case... the obvious one is marking releases branches are cumbersome to move around to, and the whole point of them is people are working on something that isn't ready to tag yet i personally tag almost every commit i hate looking at go.mod files with hexadecimal version numbers in the field
also i should mention that technically you can tag any commit, it's not branch related the relationship between commits and branches is they are blockchains (they contain the hash of the previous) tags are simply labels attached to a commit hash