Commit b5fce88e authored by Marcia Ramos's avatar Marcia Ramos

Merge branch 'docs-anchors10-user' into 'master'

Docs: Fix all anchors in /user docs

See merge request gitlab-org/gitlab-ce!25705
parents ceab79af 084d16a8
...@@ -56,7 +56,7 @@ group. That way you can have different clusters for different environments, ...@@ -56,7 +56,7 @@ group. That way you can have different clusters for different environments,
like dev, staging, production, etc. like dev, staging, production, etc.
Add another cluster similar to the first one and make sure to Add another cluster similar to the first one and make sure to
[set an environment scope](#environment-scopes) that will [set an environment scope](#environment-scopes-premium) that will
differentiate the new cluster from the rest. differentiate the new cluster from the rest.
## Base domain ## Base domain
......
...@@ -154,7 +154,7 @@ There are two different ways to add a new project to a group: ...@@ -154,7 +154,7 @@ There are two different ways to add a new project to a group:
## Transfer projects into groups ## Transfer projects into groups
Learn how to [transfer a project into a group](../project/index.md#transfer-an-existing-project-into-a-group). Learn how to [transfer a project into a group](../project/settings/index.md#transferring-an-existing-project-into-another-namespace).
## Sharing a project with a group ## Sharing a project with a group
......
# Subgroups # Subgroups
NOTE: **Note:** NOTE: **Note:**
[Introduced][ce-2772] in GitLab 9.0. Not available when using MySQL as external [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/2772) in GitLab 9.0. Not available when using MySQL as external
database (support removed in GitLab 9.3 [due to performance reasons][issue]). database (support removed in GitLab 9.3 [due to performance reasons](https://gitlab.com/gitlab-org/gitlab-ce/issues/30472#note_27747600)).
With subgroups (aka nested groups or hierarchical groups) you can have With subgroups (aka nested groups or hierarchical groups) you can have
up to 20 levels of nested groups, which among other things can help you to: up to 20 levels of nested groups, which among other things can help you to:
...@@ -13,7 +13,7 @@ up to 20 levels of nested groups, which among other things can help you to: ...@@ -13,7 +13,7 @@ up to 20 levels of nested groups, which among other things can help you to:
- **Organize large projects.** For large projects, subgroups makes it - **Organize large projects.** For large projects, subgroups makes it
potentially easier to separate permissions on parts of the source code. potentially easier to separate permissions on parts of the source code.
- **Make it easier to manage people and control visibility.** Give people - **Make it easier to manage people and control visibility.** Give people
different [permissions][] depending on their group [membership](#membership). different [permissions](../../permissions.md#group-members-permissions) depending on their group [membership](#membership).
## Database Requirements ## Database Requirements
...@@ -80,9 +80,9 @@ structure. ...@@ -80,9 +80,9 @@ structure.
NOTE: **Note:** NOTE: **Note:**
You need to be an Owner of a group in order to be able to create a subgroup. For You need to be an Owner of a group in order to be able to create a subgroup. For
more information check the [permissions table][permissions]. more information check the [permissions table](../../permissions.md#group-members-permissions).
For a list of words that are not allowed to be used as group names see the For a list of words that are not allowed to be used as group names see the
[reserved names][reserved]. [reserved names](../../reserved_names.md).
Users can always create subgroups if they are explicitly added as an Owner to Users can always create subgroups if they are explicitly added as an Owner to
a parent group even if group creation is disabled by an administrator in their a parent group even if group creation is disabled by an administrator in their
settings. settings.
...@@ -176,6 +176,6 @@ Here's a list of what you can't do with subgroups: ...@@ -176,6 +176,6 @@ Here's a list of what you can't do with subgroups:
`group/subgroup01/subgroup03`. `group/subgroup01/subgroup03`.
[ce-2772]: https://gitlab.com/gitlab-org/gitlab-ce/issues/2772 [ce-2772]: https://gitlab.com/gitlab-org/gitlab-ce/issues/2772
[permissions]: ../../permissions.md#group [permissions]: ../../permissions.md#group-members-permissions
[reserved]: ../../reserved_names.md [reserved]: ../../reserved_names.md
[issue]: https://gitlab.com/gitlab-org/gitlab-ce/issues/30472#note_27747600 [issue]: https://gitlab.com/gitlab-org/gitlab-ce/issues/30472#note_27747600
...@@ -39,7 +39,7 @@ From there, you can: ...@@ -39,7 +39,7 @@ From there, you can:
- Manage [personal access tokens](personal_access_tokens.md) to access your account via API and authorized applications - Manage [personal access tokens](personal_access_tokens.md) to access your account via API and authorized applications
- Add and delete emails linked to your account - Add and delete emails linked to your account
- Choose which email to use for notifications, web-based commits, and display on your public profile - Choose which email to use for notifications, web-based commits, and display on your public profile
- Manage [SSH keys](../../ssh/README.md#ssh) to access your account via SSH - Manage [SSH keys](../../ssh/README.md) to access your account via SSH
- Manage your [preferences](preferences.md#syntax-highlighting-theme) - Manage your [preferences](preferences.md#syntax-highlighting-theme)
to customize your own GitLab experience to customize your own GitLab experience
- [View your active sessions](active_sessions.md) and revoke any of them if necessary - [View your active sessions](active_sessions.md) and revoke any of them if necessary
......
...@@ -88,7 +88,7 @@ To add an existing Kubernetes cluster to your project: ...@@ -88,7 +88,7 @@ To add an existing Kubernetes cluster to your project:
1. Click **Add an existing Kubernetes cluster** and fill in the details: 1. Click **Add an existing Kubernetes cluster** and fill in the details:
- **Kubernetes cluster name** (required) - The name you wish to give the cluster. - **Kubernetes cluster name** (required) - The name you wish to give the cluster.
- **Environment scope** (required) - The - **Environment scope** (required) - The
[associated environment](#setting-the-environment-scope) to this cluster. [associated environment](#setting-the-environment-scope-premium) to this cluster.
- **API URL** (required) - - **API URL** (required) -
It's the URL that GitLab uses to access the Kubernetes API. Kubernetes It's the URL that GitLab uses to access the Kubernetes API. Kubernetes
exposes several APIs, we want the "base" URL that is common to all of them, exposes several APIs, we want the "base" URL that is common to all of them,
...@@ -473,7 +473,7 @@ project. That way you can have different clusters for different environments, ...@@ -473,7 +473,7 @@ project. That way you can have different clusters for different environments,
like dev, staging, production, etc. like dev, staging, production, etc.
Simply add another cluster, like you did the first time, and make sure to Simply add another cluster, like you did the first time, and make sure to
[set an environment scope](#setting-the-environment-scope) that will [set an environment scope](#setting-the-environment-scope-premium) that will
differentiate the new cluster with the rest. differentiate the new cluster with the rest.
## Setting the environment scope **[PREMIUM]** ## Setting the environment scope **[PREMIUM]**
......
...@@ -8,7 +8,7 @@ between the two, for more information consult your favorite search engine. ...@@ -8,7 +8,7 @@ between the two, for more information consult your favorite search engine.
There are two approaches to SVN to Git migration: There are two approaches to SVN to Git migration:
1. [Git/SVN Mirror](#smooth-migration-with-a-git-svn-mirror-using-subgit) which: 1. [Git/SVN Mirror](#smooth-migration-with-a-gitsvn-mirror-using-subgit) which:
- Makes the GitLab repository to mirror the SVN project. - Makes the GitLab repository to mirror the SVN project.
- Git and SVN repositories are kept in sync; you can use either one. - Git and SVN repositories are kept in sync; you can use either one.
- Smoothens the migration process and allows to manage migration risks. - Smoothens the migration process and allows to manage migration risks.
......
...@@ -137,7 +137,7 @@ and Git push/pull redirects. ...@@ -137,7 +137,7 @@ and Git push/pull redirects.
Depending on the situation, different things apply. Depending on the situation, different things apply.
When [renaming a user](../profile/index.md#changing-your-username), When [renaming a user](../profile/index.md#changing-your-username),
[changing a group path](../group/index.md#changing-a-group-s-path) or [renaming a repository](settings/index.md#renaming-a-repository): [changing a group path](../group/index.md#changing-a-groups-path) or [renaming a repository](settings/index.md#renaming-a-repository):
- Existing web URLs for the namespace and anything under it (e.g., projects) will - Existing web URLs for the namespace and anything under it (e.g., projects) will
redirect to the new URLs. redirect to the new URLs.
......
...@@ -152,7 +152,7 @@ trigger word followed by <kbd>help</kbd>. Example: <samp>/gitlab help</samp> ...@@ -152,7 +152,7 @@ trigger word followed by <kbd>help</kbd>. Example: <samp>/gitlab help</samp>
## Permissions ## Permissions
The permissions to run the [available commands](#available-slash-commands) derive from The permissions to run the [available commands](#available-slash-commands) derive from
the [permissions you have on the project](../../permissions.md#project). the [permissions you have on the project](../../permissions.md#project-members-permissions).
## Further reading ## Further reading
......
...@@ -120,7 +120,7 @@ If the "No data found" screen continues to appear, it could be due to: ...@@ -120,7 +120,7 @@ If the "No data found" screen continues to appear, it could be due to:
- No successful deployments have occurred to this environment. - No successful deployments have occurred to this environment.
- Prometheus does not have performance data for this environment, or the metrics - Prometheus does not have performance data for this environment, or the metrics
are not labeled correctly. To test this, connect to the Prometheus server and are not labeled correctly. To test this, connect to the Prometheus server and
[run a query](#gitlab-prometheus-queries), replacing `$CI_ENVIRONMENT_SLUG` [run a query](prometheus_library/kubernetes.html#metrics-supported), replacing `$CI_ENVIRONMENT_SLUG`
with the name of your environment. with the name of your environment.
[autodeploy]: ../../../ci/autodeploy/index.md [autodeploy]: ../../../ci/autodeploy/index.md
......
...@@ -59,7 +59,7 @@ which is highly recommendable and much faster than hardcoding. ...@@ -59,7 +59,7 @@ which is highly recommendable and much faster than hardcoding.
If you set up a GitLab Pages project on GitLab.com, If you set up a GitLab Pages project on GitLab.com,
it will automatically be accessible under a it will automatically be accessible under a
[subdomain of `namespace.gitlab.io`](introduction.md#gitlab-pages-on-gitlab-com). [subdomain of `namespace.gitlab.io`](introduction.md#gitlab-pages-on-gitlabcom).
The `namespace` is defined by your username on GitLab.com, The `namespace` is defined by your username on GitLab.com,
or the group name you created this project under. or the group name you created this project under.
......
...@@ -20,13 +20,13 @@ you should consider first, which we'll cover in this guide: ...@@ -20,13 +20,13 @@ you should consider first, which we'll cover in this guide:
1. Either if you're adding a **root domain** or a **subdomain**, for which 1. Either if you're adding a **root domain** or a **subdomain**, for which
you'll need to set up [DNS records](#dns-records) you'll need to set up [DNS records](#dns-records)
1. Whether you want to add an [SSL/TLS certificate](#ssl-tls-certificates) or not 1. Whether you want to add an [SSL/TLS certificate](#ssltls-certificates) or not
To finish the association, you need to [add your domain to your project's Pages settings](#add-your-custom-domain-to-gitlab-pages-settings). To finish the association, you need to [add your domain to your project's Pages settings](#add-your-custom-domain-to-gitlab-pages-settings).
Let's start from the beginning with [DNS records](#dns-records). Let's start from the beginning with [DNS records](#dns-records).
If you already know how they work and want to skip the introduction to DNS, If you already know how they work and want to skip the introduction to DNS,
you may be interested in skipping it until the [TL;DR](#tl-dr) section below. you may be interested in skipping it until the [TL;DR](#tldr) section below.
### DNS Records ### DNS Records
...@@ -148,7 +148,7 @@ verify your domain's ownership with a TXT record: ...@@ -148,7 +148,7 @@ verify your domain's ownership with a TXT record:
Once you've set the DNS record, you'll need navigate to your project's Once you've set the DNS record, you'll need navigate to your project's
**Setting > Pages** and click **+ New domain** to add your custom domain to **Setting > Pages** and click **+ New domain** to add your custom domain to
GitLab Pages. You can choose whether to add an [SSL/TLS certificate](#ssl-tls-certificates) GitLab Pages. You can choose whether to add an [SSL/TLS certificate](#ssltls-certificates)
to make your website accessible under HTTPS or leave it blank. If don't add a certificate, to make your website accessible under HTTPS or leave it blank. If don't add a certificate,
your site will be accessible only via HTTP: your site will be accessible only via HTTP:
......
...@@ -141,7 +141,7 @@ You can also take some optional further steps: ...@@ -141,7 +141,7 @@ You can also take some optional further steps:
_Advanced options:_ _Advanced options:_
- [Use a custom domain](getting_started_part_three.md#adding-your-custom-domain-to-gitlab-pages) - [Use a custom domain](getting_started_part_three.md#adding-your-custom-domain-to-gitlab-pages)
- Apply [SSL/TLS certification](getting_started_part_three.md#ssl-tls-certificates) to your custom domain - Apply [SSL/TLS certification](getting_started_part_three.md#ssltls-certificates) to your custom domain
## Explore GitLab Pages ## Explore GitLab Pages
......
...@@ -11,7 +11,7 @@ With GitLab Pages you can host for free your static websites on GitLab. ...@@ -11,7 +11,7 @@ With GitLab Pages you can host for free your static websites on GitLab.
Combined with the power of [GitLab CI] and the help of [GitLab Runner] you can Combined with the power of [GitLab CI] and the help of [GitLab Runner] you can
deploy static pages for your individual projects, your user or your group. deploy static pages for your individual projects, your user or your group.
Read [GitLab Pages on GitLab.com](#gitlab-pages-on-gitlab-com) for specific Read [GitLab Pages on GitLab.com](#gitlab-pages-on-gitlabcom) for specific
information, if you are using GitLab.com to host your website. information, if you are using GitLab.com to host your website.
## Getting started with GitLab Pages domains ## Getting started with GitLab Pages domains
...@@ -410,7 +410,7 @@ file for both the `/data` and `/data/` URL paths. ...@@ -410,7 +410,7 @@ file for both the `/data` and `/data/` URL paths.
### Add a custom domain to your Pages website ### Add a custom domain to your Pages website
For a complete guide on Pages domains, read through the article For a complete guide on Pages domains, read through the article
[GitLab Pages from A to Z: Part 3 - Setting Up Custom Domains - DNS Records and SSL/TLS Certificates](getting_started_part_three.md#setting-up-custom-domains-dns-records-and-ssl-tls-certificates) [GitLab Pages from A to Z: Part 3 - GitLab Pages custom domains and SSL/TLS Certificates](getting_started_part_three.md)
If this setting is enabled by your GitLab administrator, you should be able to If this setting is enabled by your GitLab administrator, you should be able to
see the **New Domain** button when visiting your project's settings through the see the **New Domain** button when visiting your project's settings through the
...@@ -451,7 +451,7 @@ private key when adding a new domain. ...@@ -451,7 +451,7 @@ private key when adding a new domain.
![Pages upload cert](img/pages_upload_cert.png) ![Pages upload cert](img/pages_upload_cert.png)
For a complete guide on Pages domains, read through the article For a complete guide on Pages domains, read through the article
[GitLab Pages from A to Z: Part 3 - Setting Up Custom Domains - DNS Records and SSL/TLS Certificates](getting_started_part_three.md#setting-up-custom-domains-dns-records-and-ssl-tls-certificates) [GitLab Pages from A to Z: Part 3 - GitLab Pages custom domains and SSL/TLS Certificates](getting_started_part_three.md)
### Custom error codes pages ### Custom error codes pages
......
...@@ -38,7 +38,7 @@ turn are defined with the `paths` keyword. All paths to files and directories ...@@ -38,7 +38,7 @@ turn are defined with the `paths` keyword. All paths to files and directories
are relative to the repository that was cloned during the build. These uploaded are relative to the repository that was cloned during the build. These uploaded
artifacts will be kept in GitLab for 1 week as defined by the `expire_in` artifacts will be kept in GitLab for 1 week as defined by the `expire_in`
definition. You have the option to keep the artifacts from expiring via the definition. You have the option to keep the artifacts from expiring via the
[web interface](#browsing-job-artifacts). If the expiry time is not defined, [web interface](#browsing-artifacts). If the expiry time is not defined,
it defaults to the [instance wide it defaults to the [instance wide
setting](../../admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only). setting](../../admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only).
......
...@@ -11,7 +11,7 @@ Read through GiLab's branching documentation: ...@@ -11,7 +11,7 @@ Read through GiLab's branching documentation:
See also: See also:
- [Branches API](../../../../api/branches.md), for information on operating on repository branches using the GitLab API. - [Branches API](../../../../api/branches.md), for information on operating on repository branches using the GitLab API.
- [GitLab Flow](../../../../university/training/gitlab_flow.md#gitlab-flow). Use the best of GitLab for your branching strategies. - [GitLab Flow](../../../../university/training/gitlab_flow.md). Use the best of GitLab for your branching strategies.
- [Getting started with Git](../../../../topics/git/index.md) and GitLab. - [Getting started with Git](../../../../topics/git/index.md) and GitLab.
## Default branch ## Default branch
......
...@@ -96,7 +96,7 @@ quickly access issues and merge requests created or assigned to you within that ...@@ -96,7 +96,7 @@ quickly access issues and merge requests created or assigned to you within that
Your [todos](../../workflow/todos.md#gitlab-todos) can be searched by "to do" and "done". Your [todos](../../workflow/todos.md#gitlab-todos) can be searched by "to do" and "done".
You can [filter](../../workflow/todos.md#filtering-your-todos) them per project, You can [filter](../../workflow/todos.md#filtering-your-todos) them per project,
author, type, and action. Also, you can sort them by author, type, and action. Also, you can sort them by
[**Label priority**](../../user/project/labels.md#prioritize-labels), [**Label priority**](../../user/project/labels.md#label-priority),
**Last created** and **Oldest created**. **Last created** and **Oldest created**.
## Projects ## Projects
......
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