Aboobacker MK
Aboobacker MK
@fgreinacher Here is a repo with this bug https://gitlab.com/tachyons-gitlab/semantic-bug
> it seems a bit strange to me to include the token in the remote url like that. is that still something that could be changed? This is an existing...
@travi I'm checking internally to see if there anything we can do from Gitlab's end without breaking changes. > 2025-08-21T01:41:43.490Z semantic-release:get-git-auth-url Verifying ssh auth by attempting to push to [https://gitlab-ci-token:[secure]@gitlab.com/tachyons-gitlab/semantic-bug.git](https://gitlab-ci-token:%5Bsecure%[email protected]/tachyons-gitlab/semantic-bug.git)...
If we do this on semantic release, solution would be something like ``` /** * Get the repository remote URL with any authentication credentials stripped. * * @param {Object} [execaOpts]...
@mrhornsby That is still an [open issue](https://github.com/semantic-release/gitlab/issues/156)
Could you create an PR to fix it ? On Wed, 23 Oct, 2024, 1:10 pm Darshan Poudel, ***@***.***> wrote: > ***@***.**** commented on this pull request. > ------------------------------ >...
@ParthMozarkar Could you come up with detailed description of each issues separately with screenshots and proposed fixes ?
@ShinichiShi you can pair with @blazethunderstorm
We don't need to support json endpoint for this, just html should be fine, you may specify it in the routes.rb
@ShinichiShi When you work on issue like this, create an rspec test to reproduce the bug, and then write code to fix it.