diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 12:07:59 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 12:07:59 +0300 |
commit | a325f3a104748ecc68df7c3d793940aa709a111f (patch) | |
tree | b3bce12be64ab2d9e31627dacd059165819797a3 /doc/development/packages.md | |
parent | 8fb943c7df5f2b399caaeaebd6c00d0630bc763c (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/packages.md')
-rw-r--r-- | doc/development/packages.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/packages.md b/doc/development/packages.md index 487d1243c97..848693d368a 100644 --- a/doc/development/packages.md +++ b/doc/development/packages.md @@ -75,8 +75,8 @@ that gives a way to identify the project that the package belongs to. This gener id or full project path in the package name. See [Conan's naming convention](../user/packages/conan_repository/index.md#package-recipe-naming-convention) as an example. -For group and project-level endpoints, naming can be less constrained, and it will be up to the group and project -members to be certain that there is no conflict between two package names, however the system should prevent +For group and project-level endpoints, naming can be less constrained and it will be up to the group and project +members to be certain that there is no conflict between two package names. However, the system should prevent a user from reusing an existing name within a given scope. Otherwise, naming should follow the package manager's naming conventions and include a validation in the `package.md` |