Repository navigation
Combine branch and tag push into a single push #1187
Description
Activity
I should add that I'm open to making a PR for this, if it is welcome.
I should be able to make this happen. Thanks for the willingness to help on this front but I already do have a refactor of the version command implementation underway and we would likely cause merge conflicts at the current time. I'll wrap your performance recommendation into the refactor.
Reacted by David DeepwellIt has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Still in backlog
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Started back on the performance refactor, hopefully will have this implemented in the next few months.
It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Still in backlog
It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Feature Request
Description
I was puzzled at first why I had two separate CI/CD pipelines being triggered when using the command
semantic-release version. After a little digging, lines 673-690 in thepython-semantic-release/src/semantic_release/cli/commands/version.pyfile show that two independent pushes are made; one for the branch and one for the tag.Using plain git, these can be combined into a single push, so I'm wondering if it would be possible to check for
commit_changesandcreate_tagto both be true and execute a single git push. If either are untrue, then the current functionality would be used.I am using version 9.19.1.
Use cases
This would reduce some of the network traffic and slightly speed up the command.
For those who run CI/CD pipelines triggered by individual git pushes, this would reduce duplicate pipelines. For context, I use GitLab, but run semantic-release manually, outside of a CI/CD pipeline.
Possible implementation
See the description.
Alternative solutions