Title: make tag creation optional · commitizen-tools/commitizen · Discussion #730 · GitHub
Open Graph Title: make tag creation optional · commitizen-tools/commitizen · Discussion #730
X Title: make tag creation optional · commitizen-tools/commitizen · Discussion #730
Description: make tag creation optional
Open Graph Description: Description It 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. Possible Solution we could add a config option like disable_...
X Description: Description It 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. Possible Solution we could add a config option like disable_...
Opengraph URL: https://github.com/commitizen-tools/commitizen/discussions/730
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"QAPage","mainEntity":{"@type":"Question","name":"make tag creation optional","text":"Description
\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.
\nPossible Solution
\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.
\nAdditional context
\nWe just started to use commitizen so maybe our workflow isn't the best right now.
\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:
\n\n- create new branch localy from main
\n- run
cz bump (with changelog creation) (which create a local tag on that feature branch) \n- push a merge request (just the commit without the tag) to the upstream repo
\n- have a teammate review and approve the merge request
\n- merge the merge request
\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
\n
\nBut this means we end up with tags on different commits locally than in our upstream repo.
\nWe can clean things up by running
\ngit tag -l | xargs git tag -d\ngit fetch --tags\n
\nbut it would be good to just don't mess up things in the first place.
\nAs I said, we're new to commitizen, so maybe there is an easier way to achive this
\nAdditional context
\nNo response
","upvoteCount":1,"answerCount":4,"acceptedAnswer":{"@type":"Answer","text":"That's great @TheKangaroo ! Glad to hear you found a solution!
\nFor reference in commitizen you could do:
\ncz bump --files-only --yes --changelog\ngit commit -am \"bump: release $(cz version --project)\"\nAnd later on to create the tag:
\ngit tag $(cz version --project)\n
\nCommitizen works well with git, and where commitizen is available you know git will be available, this gives you a lot of flexibility.
\nMaybe we could add this as a tutorial? 🤔
","upvoteCount":2,"url":"https://github.com/commitizen-tools/commitizen/discussions/730#discussioncomment-5754201"}}}
| route-pattern | /_view_fragments/Voltron::DiscussionsFragmentsController/show/:user_id/:repository/:discussion_number/discussion_layout(.:format) |
| route-controller | voltron_discussions_fragments |
| route-action | discussion_layout |
| fetch-nonce | v2:715455bd-07ae-dc45-9a1b-34df972f4676 |
| current-catalog-service-hash | 9f0abe34da433c9b6db74bffa2466494a717b579a96b30a5d252e5090baea7be |
| request-id | 98A6:CD4C9:183A6F6:1F96241:6976F552 |
| html-safe-nonce | e6dfefe41c1f54f633785f8cb2cbe9a5142d02c4503354fba20f6028b37bd052 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5OEE2OkNENEM5OjE4M0E2RjY6MUY5NjI0MTo2OTc2RjU1MiIsInZpc2l0b3JfaWQiOiI0MzE4MTQ1NzgwMjcyMDAyMzg2IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | bdd3091e83cfda9f1119f241209d7cabb2c79d9ae742f707f653631caf9f4492 |
| hovercard-subject-tag | discussion:5140644 |
| github-keyboard-shortcuts | repository,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/Voltron::DiscussionsFragmentsController/show/commitizen-tools/commitizen/730/discussion_layout |
| twitter:image | https://opengraph.githubassets.com/0b8fcea6763c12be22ba8069b3fff1aeca59af30232ee53f25d9dde3169106ee/commitizen-tools/commitizen/discussions/730 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/0b8fcea6763c12be22ba8069b3fff1aeca59af30232ee53f25d9dde3169106ee/commitizen-tools/commitizen/discussions/730 |
| og:image:alt | Description It 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. Possible Solution we could add a config option like disable_... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | 01d198479908d09a841b2febe8eb105a81af2af7d81830960fe0971e1f4adc09 |
| turbo-cache-control | no-preview |
| go-import | github.com/commitizen-tools/commitizen git https://github.com/commitizen-tools/commitizen.git |
| octolytics-dimension-user_id | 62252524 |
| octolytics-dimension-user_login | commitizen-tools |
| octolytics-dimension-repository_id | 106127589 |
| octolytics-dimension-repository_nwo | commitizen-tools/commitizen |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 106127589 |
| octolytics-dimension-repository_network_root_nwo | commitizen-tools/commitizen |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | f752335dbbea672610081196a1998e39aec5e14b |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width