-
Updated
Sep 25, 2020 - JavaScript
commitizen
Here are 172 public repositories matching this topic...
-
Updated
Sep 12, 2020 - TypeScript
-
Updated
Oct 8, 2020 - JavaScript
-
Updated
Oct 13, 2020 - TypeScript
-
Updated
Jun 18, 2020 - JavaScript
-
Updated
Mar 7, 2017 - JavaScript
-
Updated
Aug 27, 2017 - JavaScript
-
Updated
Sep 7, 2020 - TypeScript
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Oct 12, 2020 - PHP
-
Updated
Oct 15, 2018 - Shell
-
Updated
Jul 4, 2020 - JavaScript
-
Updated
Sep 7, 2017 - JavaScript
-
Updated
Sep 13, 2020 - JavaScript
-
Updated
Oct 13, 2020 - JavaScript
-
Updated
Sep 12, 2020 - JavaScript
-
Updated
Apr 2, 2020 - CSS
-
Updated
Sep 17, 2020 - TypeScript
-
Updated
May 23, 2020 - JavaScript
-
Updated
Sep 12, 2020 - JavaScript
-
Updated
Aug 9, 2020 - JavaScript
-
Updated
Sep 20, 2020
-
Updated
May 30, 2018 - JavaScript
-
Updated
Feb 2, 2020 - JavaScript
-
Updated
May 11, 2020 - C#
-
Updated
Oct 1, 2020 - TypeScript
-
Updated
Mar 27, 2020 - JavaScript
Improve this page
Add a description, image, and links to the commitizen topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the commitizen 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