The main question answer is: git tags. This is usually how you mark a release commit, saying: this commit marks the version "v1.0".
As for the structure of the project, for smaller ones you may need a simplified version of the common Git Workflows. Generally you work on different branches and merge when ready. The main branch has the most recent stable version.
Bi/huge teams/projects use Trunk based workflow, because the previous one have limitations. This is the opposite as previous techniques, everyone works with the master and you have release branches. The main branch has the most recent but not so stable version.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The main question answer is: git tags. This is usually how you mark a release commit, saying: this commit marks the version "v1.0".
As for the structure of the project, for smaller ones you may need a simplified version of the common Git Workflows. Generally you work on different branches and merge when ready. The main branch has the most recent stable version.
Bi/huge teams/projects use Trunk based workflow, because the previous one have limitations. This is the opposite as previous techniques, everyone works with the master and you have release branches. The main branch has the most recent but not so stable version.