Tell me, push -force tags in git is bad?

Question

git

UPD : The question can be formulated more simply:
Will there be an error when calling git pull after moving the tag to another commit has been sent to the remote repository, i.e. command:
git push -f origin some_tag_name
?
________
OLD : There is a need to create permanent branches from old commits for 1-2 commits. Merge back to master is not expected.
I don’t want to produce branches, because. there will be many such branches of 1-2 commits. But to make it easy to find commits, there is an idea to produce tags.
__A____B___C___D_______
\__A*(tag:r1.0)___A**(tag:r1.0_commented)
But I don't want to produce too many of them and I have an idea to move the tags. Those. do this:
__A____B___C___D______
\__A*(tag:r1.0)
Then, when there is a new commit:
__A____B___C___D_______
\__A*__A**(tag:r1.0)
Tell me, what will happen if you do a push-force with a tag location change? Will the others have problems doing a normal git pull command? Can there be problems when pulling from some GUI clients, can anyone come across?

Answer 1

tag - hash symbolic name
> because there will be many such branches of 1-2 commits,
how are you going to make 1-2 commits there - it's not very clear :)