codejedi365

It's a great question, I was wondering the same thing as I hit the same problem you did. I opened a PR #752, to provide an alternative workflow to not...

@tpank, luckily for you, #752, was just merged and released as part of `v8.4.0`. Let me know if it works out. Thanks for the workflow description and I did a...

@benedikt-bartscher, at the outset of your question, yes there is not a way to only push the tags but not also commit. We push the commit too. Unless I mis...

@aborsu, I appreciate you taking the initiative on this. I'll take a look more in depth tomorrow. I would rather not cause confusion between a GitLab CI and a regular...

@benedikt-bartscher, I believe this following snippet should create the workflow you desire. ```yml # .gitlab-ci.yml release: script: # Make local changes with implicit `--build`, `--commit`, `--changelog`, `--tag` & `--no-vcs-release` -...

> Does it also imply that a PAT doesn't actually work here? @sbates No, a Personal, Group or Project Access Token will work if your token permissions are correct. It...

@Exagone313, although I see your point, I don't agree with your solution. My issue is that PRs are restricted to the owner whom opened them and the maintainers. So even...

> Why is it given in every example setup? Traditionally, CI's do not have git configured automatically which will cause failures for `git` when trying to make a local commit...

The reason that the code asks the hvcs, is because previously during the configuration load step the hvcs was configured with the url from origin. Essentially they are the same...

@matthiasgleichauf, Well the type of the VCS is actually required for python-semantic-release currently. We make it optional for the user but assume GitHub when not provided. The client code sets...