codejedi365
codejedi365
> Me too, I actually spent some time looking for a similar issue and was surprised when I didn't find any 😄. Maybe this behaviour is not consistent on the...
> You mean creating a test fixture to save you some time during implementation, so you already have this test case? I can do that Yes, that's correct. I don't...
Still under development hopefully in the next few months.
@KundaPanda, this is a great contribution as you also included tests and documentation, Thank you! I just want to add a few things and we will get this merged in...
I'll take a look at it again this weekend. It got majorly complicated because it was a bit premature to add this functionality without handling all the variations of GitLab...
> Hi @codejedi365 thanks for trying to implement this properly and support all deployment variants. If you need any testing, we could test this on our gitlab instance or even...
Thanks for the update! I should be able to work on this after finishing the monorepo parser PR.
@dxvidparham, if this works, you are a hero. I've been unable to find a solution myself and as someone who cares about sustainment and security this has been frustrating to...
I think you need to set the [`semantic_release.remote.ignore_token_for_push`](https://python-semantic-release.readthedocs.io/en/latest/configuration/configuration.html#ignore-token-for-push) to `true` because of how the push command is generated (why idk and I didn't touch it if it was working). If...
Are you actually hitting an error or are you anticipating one based on my previously worded (deploy-keys unaware) guide? Regardless of what the documentation says, I am telling you that...