Commit 7ae4af48 authored by Suzanne Selhorn's avatar Suzanne Selhorn

Merge branch 'docs/composer-publish-different-projects' into 'master'

Note re. publishing Composer packages to different projects

See merge request gitlab-org/gitlab!42171
parents ca0859c5 fcc1346f
...@@ -89,3 +89,10 @@ is created, you are ready to [upload your package](../conan_repository/index.md# ...@@ -89,3 +89,10 @@ is created, you are ready to [upload your package](../conan_repository/index.md#
```shell ```shell
CONAN_LOGIN_USERNAME=<gitlab-username> CONAN_PASSWORD=<personal_access_token> conan upload MyPackage/1.0.0@foo+bar+my-proj/channel --all --remote=gitlab CONAN_LOGIN_USERNAME=<gitlab-username> CONAN_PASSWORD=<personal_access_token> conan upload MyPackage/1.0.0@foo+bar+my-proj/channel --all --remote=gitlab
``` ```
#### Composer
It is currently not possible to publish a Composer package to a project that is different from where its code resides.
If you attempt to publish a Composer package to a different project, you get a `404 Branch Not Found`
or `404 Tag Not Found` error.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment