-
Updated
Sep 25, 2020 - JavaScript
semantic-versioning
Here are 184 public repositories matching this topic...
-
Updated
Jun 9, 2020 - Go
-
Updated
Apr 7, 2018 - JavaScript
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Oct 13, 2020 - Groovy
-
Updated
Oct 12, 2020 - Python
-
Updated
Oct 25, 2019 - Java
-
Updated
Apr 21, 2020 - Python
-
Updated
May 4, 2020 - Swift
-
Updated
Oct 2, 2020 - PHP
-
Updated
Oct 7, 2020 - Go
-
Updated
Oct 11, 2020 - C++
-
Updated
Oct 9, 2020 - Python
-
Updated
Oct 13, 2020 - Java
-
Updated
Feb 12, 2020 - Groovy
-
Updated
Aug 29, 2020 - JavaScript
-
Updated
Sep 27, 2020 - Python
-
Updated
Jun 14, 2019 - Go
-
Updated
Oct 13, 2020 - JavaScript
-
Updated
Mar 4, 2020 - PHP
-
Updated
Sep 21, 2017 - Groovy
-
Updated
Aug 26, 2019 - C
-
Updated
Mar 11, 2020 - Go
-
Updated
Sep 29, 2020 - Go
-
Updated
Sep 24, 2020 - Shell
-
Updated
Sep 30, 2019 - JavaScript
-
Updated
Mar 23, 2020 - F#
-
Updated
Mar 13, 2020 - JavaScript
-
Updated
Apr 24, 2019 - Ruby
Improve this page
Add a description, image, and links to the semantic-versioning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the semantic-versioning topic, visit your repo's landing page and select "manage topics."
Description
Whenever something is merged in our main branch commitizen checks if a version bump is required. Usually it's fine but whenever no increment is detected it will still try to create a tag while it shouldn't. Because the version is still the same and matches a previously created tag the command and the pipeline fails. Am I just not handling this correctly? I can't imagine nobody has