title: Why we need semantic versioning if Git Workflow has the feature of incremented versioning?
body: <p>I'm currently learning how to implement semantic versioning for my project in Jenkins/Maven/Git, I read <a href="https://gitversion.readthedocs.io/en/latest/more-info/version-increments/" rel="nofollow noreferrer">this article</a> today, it seems like we can get incremented versioning automatically with Gitflow, what's the point of using semantic versioning then? </p>
  
  <p>I'm new to all of them, still trying to figure out the relationships among them, and I searched online for days, there's no example or tutorials regarding how to implement SV, I also read <a href="https://semver.org/" rel="nofollow noreferrer">this article</a> , I understand what SV is but still no clue how it can be linked to Jenkins/Maven/Git. I found a Jenkins plugin called semantic-versioning-plugin, but can't find anything related regarding how to implement it. </p>
  
  <p>I also tried to change the config in Jenkinsfile but it only change the build_number after every push to Git, but this is not what I want, I want the versions to follow the rules in SV. </p>
  
  <p>It would be great if someone could explain or giving me an example so I can have a look. Many thanks.</p>