René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"make tag creation optional","articleBody":"### Description\n\nIt would be great for our workflow to make it possible to opt out via config option of the creation of a git tag on `cz bump`.\r\n\n\n### Possible Solution\n\nwe could add a config option like `disable_tag_creation` (which defaults to false) to make it possible to optional disable the creation of the git tag.\n\n### Additional context\n\nWe just started to use commitizen so maybe our workflow isn't the best right now.\r\n\r\nOur GitLab rules forbid to push on main and we don't want to change that. So we needed to find a way to create releases with commitizen without pushing to main. We came up with the following workflow:\r\n* create new branch localy from main\r\n* run `cz bump` (with changelog creation) (which create a local tag on that feature branch)\r\n* push a merge request (just the commit without the tag) to the upstream repo\r\n* have a teammate review and approve the merge request\r\n* merge the merge request\r\n* a ci pipeline will run on every merge to master with commit message \"bump: version.*\" and create a gitlab release for it which also creates a git tag\r\n\r\nBut this means we end up with tags on different commits locally than in our upstream repo.\r\nWe can clean things up by running\r\n```\r\ngit tag -l | xargs git tag -d\r\ngit fetch --tags\r\n```\r\nbut it would be good to just don't mess up things in the first place.\r\n\r\nAs I said, we're new to commitizen, so maybe there is an easier way to achive this \n\n### Additional context\n\n_No response_","author":{"url":"https://github.com/TheKangaroo","@type":"Person","name":"TheKangaroo"},"datePublished":"2022-10-20T13:58:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/612/commitizen/issues/612"}