Please stop deleting the codebase for each release

It was pointed out to me that this project doesn't follow normal git management processes → - instead of committing changes as they are ready and then tagging a new release, for each release that is made the entire codebase is deleted and then re-added, with no other changes listed.

While it is recommended to handle changes via public issues. there's nothing to stop you from committing a lot of changes in one go. However, deleting the entire codebase and re-adding it does nothing but make it following and using the codebase a lot more cumbersome than it needs to be. It's a bad way of managing the codebase.

If you're not going to handle changes via public issues can you please at least consider not deleting everything before committing new changes? All you have to do is delete all the files locally (rm -rf *), add the new files into the empty directory, add all the changes (git add .) and then commit everything (git commit); this way people using the module will have an easier time with the codebase.