Ehi @rutshah, what's the correct avenue to demonstrate interest as customers?
Retried in GitLab v17.11.1, it does correctly output an error for "Key already taken".
I'm wrestling with this issue from time to time, so today I tried a PoC to see if I was able to reproduce. I couldn't, but then I noticed a difference with my colleagues' project where they were having it: I generated the composer.lock with the --prefer-dist option, which in turn generates a https://gitlab.example.com... url value in the composer.lock under source.url field, instead of the [email protected]... format.
IIRC Composer has to use Git to clone in the second case, but it's able to go through the GitLab API in the former, so in that case I was able to use the CI_JOB_TOKEN with no issues. Required project is internal in a private, self-hosted instance.
Alessandro Lai (a911024c) at 12 Feb 11:56
Add readme note
Alessandro Lai (719bb420) at 24 Oct 17:05
Hello codemotion
Alessandro Lai (9188cfb3) at 18 Oct 17:57
Add GitLab deployment annotations
Alessandro Lai (9188cfb3) at 18 Oct 17:57
Add GitLab deployment annotations
Alessandro Lai (9188cfb3) at 18 Oct 17:57
Add GitLab deployment annotations
Alessandro Lai (c626a042) at 18 Oct 08:47
Live demo
Alessandro Lai (ae77de63) at 18 Oct 06:15
Fix deployment stop job
Alessandro Lai (ae77de63) at 18 Oct 06:15
Fix deployment stop job
Alessandro Lai (ae77de63) at 18 Oct 06:14
Fix deployment stop job
Alessandro Lai (c8e5b36e) at 18 Oct 06:00
Add README and docker-compose.override.yml.dist
... and 4 more commits