Is it ok to use branches to backup the application version?

Question

git

I'm trying to actively implement git in coding and a question arose.
Usually, in order to try a feature, they create a branch, do everything in it, test it, and if it's ok - merge with the master.
And if such a case is a working code in the master, but you want to remove the feature, on the contrary, most likely. Does the option to create a branch with the old version, then return to the master (well, or a third branch with a feature that will fly to the master anyway) and delete the most likely-unnecessary-feature there has the right to life? In total, we will have the old code in the branch, just in case.

Answer 1

Tags can be used to mark any significant versions. You don't have to create an entire thread for this.
And adding a feature to the master is essentially no different from removing legacy or refactoring. Branch --> changes --> merge.