Коммит f1ce7db0 создал по автору Fiona Neill's avatar Fiona Neill Зафиксировано автором Russell Dickenson
Просмотр файлов

Move Namespace content to its own page

владелец 67088fd4
Скрыть пробелы
Построчно Рядом
doc/api/namespaces.md
Просмотр файла @ f1ce7db0
......@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Namespaces API **(FREE)**
Usernames and group names fall under a special category called
[namespaces](../user/group/index.md#namespaces).
[namespaces](../user/namespace/index.md).
For users and groups supported API calls see the [users](users.md) and
[groups](groups.md) documentation respectively.
......
doc/ci/pipelines/cicd_minutes.md
Просмотр файла @ f1ce7db0
......@@ -21,7 +21,7 @@ On GitLab.com:
- CI/CD minutes quotas are enabled for both public and private projects, but public
projects [consume CI/CD minutes at a slower rate](#cost-factor).
- The base monthly CI/CD minutes quota for a GitLab.com [namespace](../../user/group/index.md#namespaces)
- The base monthly CI/CD minutes quota for a GitLab.com [namespace](../../user/namespace/index.md)
is determined by its [license tier](https://about.gitlab.com/pricing/).
- You can [purchase additional CI/CD minutes](#purchase-additional-cicd-minutes)
if you need more than the number of CI/CD minutes in your monthly quota.
......
doc/development/namespaces_storage_statistics.md
Просмотр файла @ f1ce7db0
......@@ -14,7 +14,7 @@ storage consumed by a group, and allow easy management.
## Proposal
1. Create a new ActiveRecord model to hold the namespaces' statistics in an aggregated form (only for root [namespaces](../user/group/index.md#namespaces)).
1. Create a new ActiveRecord model to hold the namespaces' statistics in an aggregated form (only for root [namespaces](../user/namespace/index.md)).
1. Refresh the statistics in this model every time a project belonging to this namespace is changed.
## Problem
......
doc/topics/git/terminology.md
Просмотр файла @ f1ce7db0
......@@ -31,7 +31,7 @@ This copy is called a [**fork**](../../user/project/repository/forking_workflow.
The process is called "creating a fork."
When you fork a repository, you create a copy of the project in your own
[namespace](../../user/group/#namespaces). You then have write permissions to modify the project files
[namespace](../../user/namespace/index.md). You then have write permissions to modify the project files
and settings.
For example, you can fork this project, <https://gitlab.com/gitlab-tests/sample-project/>, into your namespace.
......
doc/tutorials/move_personal_project_to_a_group.md
Просмотр файла @ f1ce7db0
......@@ -24,7 +24,7 @@ A group gives you some great benefits. For example, you can:
However, if you're working in a [personal project](../user/project/working_with_projects.md#view-personal-projects),
you can't use these features. Personal projects are created under your
[personal namespace](../user/group/index.md#namespaces). They're not part of a group,
[personal namespace](../user/namespace/index.md). They're not part of a group,
so you can't get any of the benefits and features of a group.
But don't worry! You can move your existing personal project to a group.
......
doc/user/free_user_limit.md
Просмотр файла @ f1ce7db0
......@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Free user limit **(FREE SAAS)**
From September 15, 2022, namespaces in GitLab.com on the Free tier
will be limited to five (5) members per [namespace](group/index.md#namespaces).
will be limited to five (5) members per [namespace](namespace/index.md).
This limit applies to top-level groups and personal namespaces.
In a personal namespace, the limit applies across all projects in your personal
......
doc/user/group/index.md
Просмотр файла @ f1ce7db0
......@@ -35,19 +35,6 @@ empty for anonymous users. The group page has a visibility level icon.
Administrator users cannot create a subgroup or project with a higher visibility level than that of
the immediate parent group.
## Namespaces
In GitLab, a namespace is a unique name for a user, a group, or subgroup under
which a project can be created.
For example, consider a user named Alex:
| GitLab URL | Namespace |
| ---------- | --------- |
| Alex creates an account with the username `alex`: `https://gitlab.example.com/alex`. | The namespace in this case is `alex`. |
| Alex creates a group for their team with the group name `alex-team`. The group and its projects are available at: `https://gitlab.example.com/alex-team`. | The namespace in this case is `alex-team`. |
| Alex creates a subgroup of `alex-team` with the subgroup name `marketing`. The subgroup and its projects are available at: `https://gitlab.example.com/alex-team/marketing`. | The namespace in this case is `alex-team/marketing`. |
## Related topics
- [Group wikis](../project/wiki/index.md)
......
doc/user/group/manage.md
Просмотр файла @ f1ce7db0
......@@ -18,7 +18,7 @@ To create a group:
1. Select **Create group**.
1. Enter a name for the group in **Group name**. For a list of words that cannot be used as group names, see
[reserved names](../reserved_names.md).
1. Enter a path for the group in **Group URL**, which is used for the [namespace](index.md#namespaces).
1. Enter a path for the group in **Group URL**, which is used for the [namespace](../namespace/index.md).
1. Choose the [visibility level](../public_access.md).
1. Personalize your GitLab experience by answering the following questions:
- What is your role?
......
doc/user/namespace/index.md 0 → 100644
Просмотр файла @ f1ce7db0
---
stage: Manage
group: Workspace
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Namespaces
In GitLab, a namespace is a unique name for a user, a [group](../group/index.md), or [subgroup](../group/subgroups/index.md) under
which a project can be created.
For example, consider a user named Alex:
| GitLab URL | Namespace |
| ---------- | --------- |
| Alex creates an account with the username `alex`: `https://gitlab.example.com/alex`. | The namespace in this case is `alex`. |
| Alex [creates a group](../group/manage.md#create-a-group) for their team with the group name `alex-team`. The group and its projects are available at: `https://gitlab.example.com/alex-team`. | The namespace in this case is `alex-team`. |
| Alex [creates a subgroup](../group/subgroups/index.md#create-a-subgroup) of `alex-team` with the subgroup name `marketing`. The subgroup and its projects are available at: `https://gitlab.example.com/alex-team/marketing`. | The namespace in this case is `alex-team/marketing`. |
doc/user/packages/composer_repository/index.md
Просмотр файла @ f1ce7db0
......@@ -44,7 +44,7 @@ a group's namespace, rather than a user's namespace. Composer packages
1. Run [`composer init`](https://getcomposer.org/doc/03-cli.md#init) and answer the prompts.
For namespace, enter your unique [namespace](../../../user/group/index.md#namespaces), like your GitLab username or group name.
For namespace, enter your unique [namespace](../../../user/namespace/index.md), like your GitLab username or group name.
A file called `composer.json` is created:
......
doc/user/packages/terraform_module_registry/index.md
Просмотр файла @ f1ce7db0
......@@ -101,7 +101,7 @@ module "<module>" {
}
```
Where `<namespace>` is the [namespace](../../../user/group/index.md#namespaces) of the Terraform module registry.
Where `<namespace>` is the [namespace](../../../user/namespace/index.md) of the Terraform module registry.
## Publish a Terraform module by using CI/CD
......@@ -125,7 +125,7 @@ upload:
script:
- TERRAFORM_MODULE_NAME=$(echo "${TERRAFORM_MODULE_NAME}" | tr " _" -) # module-name must not have spaces or underscores, so translate them to hyphens
- tar -vczf ${TERRAFORM_MODULE_NAME}-${TERRAFORM_MODULE_SYSTEM}-${TERRAFORM_MODULE_VERSION}.tgz -C ${TERRAFORM_MODULE_DIR} --exclude=./.git .
- 'curl --location --header "JOB-TOKEN: ${CI_JOB_TOKEN}"
- 'curl --location --header "JOB-TOKEN: ${CI_JOB_TOKEN}"
--upload-file ${TERRAFORM_MODULE_NAME}-${TERRAFORM_MODULE_SYSTEM}-${TERRAFORM_MODULE_VERSION}.tgz
${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/terraform/modules/${TERRAFORM_MODULE_NAME}/${TERRAFORM_MODULE_SYSTEM}/${TERRAFORM_MODULE_VERSION}/file'
rules:
......
doc/user/permissions.md
Просмотр файла @ f1ce7db0
......@@ -42,7 +42,7 @@ available only:
- For group owners. The role is inherited for a group's projects.
- For Administrators.
Personal [namespace](group/index.md#namespaces) owners:
Personal [namespace](namespace/index.md) owners:
- Are displayed as having the Maintainer role on projects in the namespace, but have the same permissions as a user with the Owner role.
- In GitLab 14.9 and later, for new projects in the namespace, are displayed as having the Owner role.
......
doc/user/profile/index.md
Просмотр файла @ f1ce7db0
......@@ -40,7 +40,7 @@ If you don't know your current password, select the **I forgot my password** lin
## Change your username
Your username has a unique [namespace](../group/index.md#namespaces),
Your username has a unique [namespace](../namespace/index.md),
which is updated when you change your username. Before you change your username, read about
[how redirects behave](../project/repository/index.md#what-happens-when-a-repository-path-changes).
If you do not want to update the namespace, you can create a new user or group and transfer projects to it instead.
......
doc/user/project/members/index.md
Просмотр файла @ f1ce7db0
......@@ -107,7 +107,7 @@ The members of the group are not displayed on the **Members** tab.
The **Members** tab shows:
- Members who are directly assigned to the project.
- If the project was created in a group [namespace](../../group/index.md#namespaces), members of that group.
- If the project was created in a group [namespace](../../namespace/index.md), members of that group.
## Import users from another project
......
doc/user/project/pages/getting_started_part_one.md
Просмотр файла @ f1ce7db0
......@@ -18,7 +18,7 @@ replace the Pages wildcard domain on GitLab.com (`*.gitlab.io`) with your own.
If you set up a GitLab Pages project on GitLab,
it's automatically accessible under a
subdomain of `namespace.example.io`.
The [`namespace`](../../group/index.md#namespaces)
The [`namespace`](../../namespace/index.md)
is defined by your username on GitLab.com,
or the group name you created this project under.
For GitLab self-managed instances, replace `example.io`
......
doc/user/project/repository/forking_workflow.md
Просмотр файла @ f1ce7db0
......@@ -26,7 +26,7 @@ To fork an existing project in GitLab:
1. On the project's home page, in the top right, select **{fork}** **Fork**:
![Fork this project](img/forking_workflow_fork_button_v13_10.png)
1. Optional. Edit the **Project name**.
1. For **Project URL**, select the [namespace](../../group/index.md#namespaces)
1. For **Project URL**, select the [namespace](../../namespace/index.md)
your fork should belong to.
1. Add a **Project slug**. This value becomes part of the URL to your fork.
It must be unique in the namespace.
......
doc/user/project/working_with_projects.md
Просмотр файла @ f1ce7db0
......@@ -233,7 +233,7 @@ To push your repository and create a project:
```
- For `gitlab.example.com`, use the domain name of the machine that hosts your Git repository.
- For `namespace`, use the name of your [namespace](../group/index.md#namespaces).
- For `namespace`, use the name of your [namespace](../namespace/index.md).
- For `myproject`, use the name of your project.
- Optional. To export existing repository tags, append the `--tags` flag to your `git push` command.
1. Optional. To configure the remote:
......@@ -371,7 +371,7 @@ To leave a project:
1. Select a project.
1. Select **Leave project**. The **Leave project** option only displays
on the project dashboard when a project is part of a group under a
[group namespace](../group/index.md#namespaces).
[group namespace](../namespace/index.md).
## Use a project as a Go package
......
doc/user/usage_quotas.md
Просмотр файла @ f1ce7db0
......@@ -67,7 +67,7 @@ you must purchase additional storage. For more details, see [Excess storage usag
## View storage usage
You can view storage usage for your project or [namespace](../user/group/#namespaces).
You can view storage usage for your project or [namespace](../user/namespace/index.md).
1. Go to your project or namespace:
- For a project, on the top bar, select **Menu > Projects** and find your project.
......
doc/user/workspace/index.md
Просмотр файла @ f1ce7db0
......@@ -17,7 +17,7 @@ sole discretion of GitLab Inc.
NOTE:
Workspace is currently in development.
Workspace will be above the [top-level namespaces](../group/index.md#namespaces) for you to manage
Workspace will be above the [top-level namespaces](../namespace/index.md) for you to manage
everything you do as a GitLab administrator, including:
- Defining and applying settings to all of your groups, subgroups, and projects.
......
Поддерживает Markdown
0% или .
You are about to add 0 people to the discussion. Proceed with caution.
Сначала завершите редактирование этого сообщения!
Пожалуйста, зарегистрируйтесь или чтобы прокомментировать