Merge branch 'docs-image-alignment-2' into 'master'
Fix markdown spacing in various docs (part 4) See merge request gitlab-org/gitlab-ce!31710
This commit is contained in:
Achilleas Pipinellis
commit
95075fee78
|
|
@ -91,11 +91,11 @@ To create a new Group, either:
|
|||
|
||||
- In the top menu, click **Groups** and then **Your Groups**, and click the green button **New group**.
|
||||
|
||||
|
||||
|
||||
|
||||
- Or, in the top menu, expand the `plus` sign and choose **New group**.
|
||||
|
||||
|
||||
|
||||
|
||||
Add the following information:
|
||||
|
||||
|
|
@ -104,15 +104,15 @@ Add the following information:
|
|||
1. The **Group name** will automatically populate the URL. Optionally, you can change it.
|
||||
This is the name that displays in group views.
|
||||
The name can contain only:
|
||||
- Alphanumeric characters
|
||||
- Underscores
|
||||
- Dashes and dots
|
||||
- Spaces
|
||||
- Alphanumeric characters
|
||||
- Underscores
|
||||
- Dashes and dots
|
||||
- Spaces
|
||||
1. The **Group URL** is the namespace under which your projects will be hosted.
|
||||
The URL can contain only:
|
||||
- Alphanumeric characters
|
||||
- Underscores
|
||||
- Dashes and dots (it cannot start with dashes or end in a dot)
|
||||
- Alphanumeric characters
|
||||
- Underscores
|
||||
- Dashes and dots (it cannot start with dashes or end in a dot)
|
||||
1. Optionally, you can add a brief description to tell others
|
||||
what this group is about.
|
||||
1. Optionally, choose an avatar for your group.
|
||||
|
|
@ -166,12 +166,12 @@ There are two different ways to add a new project to a group:
|
|||
|
||||
- Select a group, and then click **New project**. You can then continue [creating your project](../../gitlab-basics/create-project.md).
|
||||
|
||||
|
||||
|
||||
|
||||
- While you are creating a project, select a group namespace
|
||||
you've already created from the dropdown menu.
|
||||
|
||||
|
||||
|
||||
|
||||
### Default project-creation level
|
||||
|
||||
|
|
|
|||
|
|
@ -90,11 +90,11 @@ You can then test the connection by clicking on **Test Connection**. If the conn
|
|||
1. Create a new mapping by clicking **Add New Mapping** then set **Source attribute** to `objectId`, and **Target attribute** to `externalId`.
|
||||
1. Click the `userPrincipalName` mapping and change **Match objects using this attribute** to `No`.
|
||||
|
||||
Save your changes and you should have the following configuration:
|
||||
Save your changes and you should have the following configuration:
|
||||
|
||||
|
||||
|
||||
NOTE: **Note:** If you used a unique identifier **other than** `objectId`, be sure to map it instead to both `id` and `externalId`.
|
||||
NOTE: **Note:** If you used a unique identifier **other than** `objectId`, be sure to map it instead to both `id` and `externalId`.
|
||||
|
||||
1. Below the mapping list click on **Show advanced options > Edit attribute list for AppName**.
|
||||
1. Leave the `id` as the primary and only required field.
|
||||
|
|
@ -108,7 +108,7 @@ You can then test the connection by clicking on **Test Connection**. If the conn
|
|||
1. Save all the screens and, in the **Provisioning** step, set
|
||||
the `Provisioning Status` to `On`.
|
||||
|
||||
|
||||
|
||||
|
||||
NOTE: **Note:**
|
||||
You can control what is actually synced by selecting the `Scope`. For example,
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ To lock a file:
|
|||
1. Pick the file you want to lock.
|
||||
1. Click the "Lock" button.
|
||||
|
||||
|
||||
|
||||
|
||||
To lock an entire directory, look for the "Lock" link next to "History".
|
||||
|
||||
|
|
|
|||
|
|
@ -49,17 +49,17 @@ namespace that started the import process.
|
|||
|
||||
1. Click on the "Bitbucket Cloud" button.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Grant GitLab access to your Bitbucket account
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click on the projects that you'd like to import or **Import all projects**.
|
||||
You can also select the namespace under which each project will be
|
||||
imported.
|
||||
|
||||
|
||||
|
||||
|
||||
[bb-import]: ../../../integration/bitbucket.md
|
||||
[social sign-in]: ../../profile/account/social_sign_in.md
|
||||
|
|
|
|||
|
|
@ -59,16 +59,16 @@ namespace that started the import process.
|
|||
1. Sign in to GitLab and go to your dashboard.
|
||||
1. Click on **New project**.
|
||||
1. Click on the "Bitbucket Server" button. If the button is not present, enable the importer in
|
||||
**Admin > Application Settings > Visibility and access controls > Import sources**.
|
||||
**Admin > Application Settings > Visibility and access controls > Import sources**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Enter your Bitbucket Server credentials.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click on the projects that you'd like to import or **Import all projects**.
|
||||
You can also select the namespace under which each project will be
|
||||
imported.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -5,13 +5,17 @@ instance or GitLab.com.
|
|||
|
||||
## Why is Gemnasium.com closed?
|
||||
|
||||
Gemnasium has been [acquired by GitLab](https://about.gitlab.com/press/releases/2018-01-30-gemnasium-acquisition.html)
|
||||
Gemnasium was [acquired by GitLab](https://about.gitlab.com/press/releases/2018-01-30-gemnasium-acquisition.html)
|
||||
in January 2018. Since May 15, 2018, the services provided by Gemnasium are no longer available.
|
||||
The team behind Gemnasium has joined GitLab as the new Security Products team
|
||||
and is working on a wider range of tools than just Dependency Scanning:
|
||||
[SAST](../../application_security/sast/index.md),
|
||||
[DAST](../../application_security/dast/index.md),
|
||||
[Container Scanning](../../application_security/container_scanning/index.md) and more.
|
||||
and is working on a [wide range of tools](../../application_security/index.md),
|
||||
including:
|
||||
|
||||
- [Dependency Scanning](../../application_security/dependency_scanning/index.md)
|
||||
- [SAST](../../application_security/sast/index.md)
|
||||
- [DAST](../../application_security/dast/index.md)
|
||||
- [Container Scanning](../../application_security/container_scanning/index.md)
|
||||
|
||||
If you want to continue monitoring your dependencies, see the
|
||||
[Migrating to GitLab](#migrating-to-gitlab) section below.
|
||||
|
||||
|
|
@ -57,27 +61,27 @@ back to both GitLab and GitHub when completed.
|
|||
|
||||
1. Create a new project, and select the "CI/CD for external repo" tab:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Use the "GitHub" button to connect your repositories.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select the project(s) to be set up with GitLab CI/CD and chose "Connect".
|
||||
|
||||
|
||||
|
||||
|
||||
Once the configuration is done, you may click on your new
|
||||
project on GitLab.
|
||||
Once the configuration is done, you may click on your new
|
||||
project on GitLab.
|
||||
|
||||
|
||||
|
||||
|
||||
Your project is now mirrored on GitLab, where the Runners will be able to access
|
||||
your source code and run your tests.
|
||||
Your project is now mirrored on GitLab, where the Runners will be able to access
|
||||
your source code and run your tests.
|
||||
|
||||
Optional step: If you set this up on GitLab.com, make sure the project is
|
||||
public (in the project settings) if your GitHub project is public, since
|
||||
the security feature is available only for [GitLab Ultimate](https://about.gitlab.com/pricing).
|
||||
Optional step: If you set this up on GitLab.com, make sure the project is
|
||||
public (in the project settings) if your GitHub project is public, since
|
||||
the security feature is available only for [GitLab Ultimate](https://about.gitlab.com/pricing).
|
||||
|
||||
1. To set up the dependency scanning job, corresponding to what Gemnasium was
|
||||
doing, you must create a `.gitlab-ci.yml` file, or update it according to
|
||||
|
|
@ -85,16 +89,16 @@ back to both GitLab and GitHub when completed.
|
|||
The mirroring is pull-only by default, so you may create or update the file on
|
||||
GitHub:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Once your file has been committed, a new pipeline will be automatically
|
||||
triggered if your file is valid:
|
||||
|
||||
|
||||
|
||||
|
||||
1. The result of the job will be visible directly from the pipeline view:
|
||||
|
||||
|
||||
|
||||
|
||||
NOTE: **Note:**
|
||||
If you don't commit very often to your project, you may want to use
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
# Import multiple repositories by uploading a manifest file
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/28811) in
|
||||
GitLab 11.2.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/28811) in GitLab 11.2.
|
||||
|
||||
GitLab allows you to import all the required Git repositories
|
||||
based on a manifest file like the one used by the
|
||||
|
|
@ -56,4 +55,4 @@ You can start the import with:
|
|||
to the import status page with projects list based on the manifest file.
|
||||
1. Check the list and click **Import all repositories** to start the import.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -40,17 +40,13 @@ the administrator console.
|
|||
1. Log in with an account that has admin privileges and navigate to the system
|
||||
console.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
1. Click **Custom integrations** and set **Enable Custom Slash Commands**,
|
||||
**Enable custom integrations to override usernames**, and **Override
|
||||
custom integrations to override profile picture icons** to true
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
1. Click **Save** at the bottom to save the changes.
|
||||
|
||||
|
|
@ -62,14 +58,12 @@ the administrator console.
|
|||
A screen will appear with all the values you need to copy in Mattermost as
|
||||
described in the next step. Leave the window open.
|
||||
|
||||
>**Note:**
|
||||
GitLab will propose some values for the Mattermost settings. The only one
|
||||
required to copy-paste as-is is the **Request URL**, all the others are just
|
||||
suggestions.
|
||||
NOTE: **Note:**
|
||||
GitLab will propose some values for the Mattermost settings. The only one
|
||||
required to copy-paste as-is is the **Request URL**, all the others are just
|
||||
suggestions.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
1. Proceed to the next step and create a slash command in Mattermost with the
|
||||
above values.
|
||||
|
|
@ -83,44 +77,38 @@ in a new slash command.
|
|||
1. Back to Mattermost, under your team page settings, you should see the
|
||||
**Integrations** option.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
1. Go to the **Slash Commands** integration and add a new one by clicking the
|
||||
**Add Slash Command** button.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
1. Fill in the options for the custom command as described in
|
||||
[step 2](#step-2-open-the-mattermost-slash-commands-service-in-gitlab).
|
||||
|
||||
>**Note:**
|
||||
If you plan on connecting multiple projects, pick a slash command trigger
|
||||
word that relates to your projects such as `/gitlab-project-name` or even
|
||||
just `/project-name`. Only use `/gitlab` if you will only connect a single
|
||||
project to your Mattermost team.
|
||||
NOTE: **Note:**
|
||||
If you plan on connecting multiple projects, pick a slash command trigger
|
||||
word that relates to your projects such as `/gitlab-project-name` or even
|
||||
just `/project-name`. Only use `/gitlab` if you will only connect a single
|
||||
project to your Mattermost team.
|
||||
|
||||
|
||||
|
||||
|
||||
1. After you set up all the values, copy the token (we will use it below) and
|
||||
click **Done**.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 4. Copy the Mattermost token into the Mattermost slash command service
|
||||
|
||||
1. In GitLab, paste the Mattermost token you copied in the previous step and
|
||||
check the **Active** checkbox.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Save changes** for the changes to take effect.
|
||||
|
||||
---
|
||||
|
||||
You are now set to start using slash commands in Mattermost that talk to the
|
||||
GitLab project you configured.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,18 +5,18 @@
|
|||
the **Redmine** service, and fill in the required details on the page as described
|
||||
in the table below.
|
||||
|
||||
| Field | Description |
|
||||
| ----- | ----------- |
|
||||
| `description` | A name for the issue tracker (to differentiate between instances, for example) |
|
||||
| `project_url` | The URL to the project in Redmine which is being linked to this GitLab project |
|
||||
| `issues_url` | The URL to the issue in Redmine project that is linked to this GitLab project. Note that the `issues_url` requires `:id` in the URL. This ID is used by GitLab as a placeholder to replace the issue number. |
|
||||
| `new_issue_url` | This is the URL to create a new issue in Redmine for the project linked to this GitLab project. **This is currently not being used and will be removed in a future release.** |
|
||||
| Field | Description |
|
||||
| ----- | ----------- |
|
||||
| `description` | A name for the issue tracker (to differentiate between instances, for example) |
|
||||
| `project_url` | The URL to the project in Redmine which is being linked to this GitLab project |
|
||||
| `issues_url` | The URL to the issue in Redmine project that is linked to this GitLab project. Note that the `issues_url` requires `:id` in the URL. This ID is used by GitLab as a placeholder to replace the issue number. |
|
||||
| `new_issue_url` | This is the URL to create a new issue in Redmine for the project linked to this GitLab project. **This is currently not being used and will be removed in a future release.** |
|
||||
|
||||
Once you have configured and enabled Redmine you'll see the Redmine link on the GitLab project pages that takes you to the appropriate Redmine project.
|
||||
Once you have configured and enabled Redmine you'll see the Redmine link on the GitLab project pages that takes you to the appropriate Redmine project.
|
||||
|
||||
As an example, below is a configuration for a project named gitlab-ci.
|
||||
As an example, below is a configuration for a project named gitlab-ci.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To disable the internal issue tracking system in a project, navigate to the General page, expand the [permissions](../settings/index.md#sharing-and-permissions) section and switch the **Issues** toggle to disabled.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,18 +20,18 @@ To share 'Project Acme' with the 'Engineering' group:
|
|||
|
||||
1. For 'Project Acme' use the left navigation menu to go to **Settings > Members**
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select the 'Share with group' tab
|
||||
1. Add the 'Engineering' group with the maximum access level of your choice
|
||||
1. Click **Share** to share it
|
||||
|
||||
|
||||
|
||||
|
||||
1. After sharing 'Project Acme' with 'Engineering', the project will be listed
|
||||
on the group dashboard
|
||||
|
||||
|
||||
|
||||
|
||||
Note that you can only share a project with:
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ To edit the merge request approvals:
|
|||
1. Navigate to your project's **Settings > General** and expand
|
||||
**Merge request approvals**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Edit**.
|
||||
1. Search for users or groups that will be [eligible to approve](#eligible-approvers)
|
||||
|
|
@ -54,7 +54,7 @@ To edit the merge request approvals:
|
|||
box. Note: the minimum can be 0.
|
||||
1. Click **Update approvers**.
|
||||
|
||||
|
||||
|
||||
|
||||
The steps above are the minimum required to get approvals working in your
|
||||
merge requests, but there are a couple more options available that might be
|
||||
|
|
@ -83,7 +83,7 @@ request approval rules:
|
|||
1. Give the approval rule a name that describes the set of approvers selected.
|
||||
1. Click **Add approvers** to submit the new rule.
|
||||
|
||||
|
||||
|
||||
|
||||
## Multiple approval rules **(PREMIUM)**
|
||||
|
||||
|
|
@ -144,14 +144,17 @@ the following is possible:
|
|||
|
||||
- If the required number of approvals has _not_ been yet met, they can approve
|
||||
it by clicking the displayed **Approve** button.
|
||||
|
||||
|
||||
|
||||
|
||||
- If the required number of approvals has already been met, they can still
|
||||
approve it by clicking the displayed **Approve additionally** button.
|
||||
|
||||
|
||||
|
||||
|
||||
- **They have already approved this merge request**: They can remove their approval.
|
||||
|
||||
|
||||
|
||||
|
||||
NOTE: **Note:**
|
||||
The merge request author is only allowed to approve their own merge request
|
||||
|
|
@ -159,7 +162,7 @@ if [**Prevent author approval**](#allowing-merge-request-authors-to-approve-thei
|
|||
|
||||
For a given merge request, if the approval restrictions have been satisfied,
|
||||
the merge request is unblocked and can be merged.
|
||||
Note, that meeting the required number of approvals is a necessary, but not
|
||||
Note that meeting the required number of approvals is a necessary, but not
|
||||
sufficient condition for unblocking a merge request from being merged. There
|
||||
are other conditions that may block it, such as merge conflicts,
|
||||
[pending discussions](../../discussions/index.md#only-allow-merge-requests-to-be-merged-if-all-threads-are-resolved)
|
||||
|
|
@ -203,7 +206,7 @@ First, you have to enable this option in the project's settings:
|
|||
1. Tick the "Can override approvers and approvals required per merge request"
|
||||
checkbox
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Save changes**
|
||||
|
||||
|
|
@ -259,7 +262,7 @@ new commits are pushed to the source branch of the merge request:
|
|||
1. Tick the "Remove all approvals in a merge request when new commits are pushed to its source branch"
|
||||
checkbox
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Save changes**
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Once you've met the requirements, to enable Let's Encrypt integration:
|
|||
1. Click **Edit** in the top-right corner.
|
||||
1. Enable Let's Encrypt integration by switching **Automatic certificate management using Let's Encrypt**:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Save changes**.
|
||||
|
||||
|
|
|
|||
|
|
@ -86,17 +86,17 @@ You can also take some **optional** further steps:
|
|||
|
||||
- _Remove the fork relationship._ The fork relationship is necessary to contribute back to the project you originally forked from. If you don't have any intentions to do so, you can remove it. To do so, navigate to your project's **Settings**, expand **Advanced settings**, and scroll down to **Remove fork relationship**:
|
||||
|
||||
|
||||
|
||||
|
||||
- _Make it a user or group website._ To turn a **project website** forked
|
||||
from the Pages group into a **user/group** website, you'll need to:
|
||||
- Rename it to `namespace.gitlab.io`: go to your project's
|
||||
**Settings > General** and expand **Advanced**. Scroll down to
|
||||
**Rename repository** and change the path to `namespace.gitlab.io`.
|
||||
- Adjust your SSG's [base URL](#urls-and-baseurls) from `"project-name"` to
|
||||
`""`. This setting will be at a different place for each SSG, as each of them
|
||||
have their own structure and file tree. Most likely, it will be in the SSG's
|
||||
config file.
|
||||
- Rename it to `namespace.gitlab.io`: go to your project's
|
||||
**Settings > General** and expand **Advanced**. Scroll down to
|
||||
**Rename repository** and change the path to `namespace.gitlab.io`.
|
||||
- Adjust your SSG's [base URL](#urls-and-baseurls) from `"project-name"` to
|
||||
`""`. This setting will be at a different place for each SSG, as each of them
|
||||
have their own structure and file tree. Most likely, it will be in the SSG's
|
||||
config file.
|
||||
|
||||
### Create a project from scratch
|
||||
|
||||
|
|
@ -107,12 +107,12 @@ You can also take some **optional** further steps:
|
|||
files to your project, add, commit and push to GitLab.
|
||||
1. From the your **Project**'s page, click **Set up CI/CD**:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Choose one of the templates from the dropbox menu.
|
||||
Pick up the template corresponding to the SSG you're using (or plain HTML).
|
||||
|
||||
|
||||
|
||||
|
||||
Once you have both site files and `.gitlab-ci.yml` in your project's
|
||||
root, GitLab CI/CD will build your site and deploy it with Pages.
|
||||
|
|
@ -123,20 +123,20 @@ where you'll find its default URL.
|
|||
> **Notes:**
|
||||
>
|
||||
> - GitLab Pages [supports any SSG](https://about.gitlab.com/2016/06/17/ssg-overview-gitlab-pages-part-3-examples-ci/), but,
|
||||
if you don't find yours among the templates, you'll need
|
||||
to configure your own `.gitlab-ci.yml`. To do that, please
|
||||
read through the article [Creating and Tweaking GitLab CI/CD for GitLab Pages](getting_started_part_four.md). New SSGs are very welcome among
|
||||
the [example projects](https://gitlab.com/pages). If you set
|
||||
up a new one, please
|
||||
[contribute](https://gitlab.com/pages/pages.gitlab.io/blob/master/CONTRIBUTING.md)
|
||||
to our examples.
|
||||
> if you don't find yours among the templates, you'll need
|
||||
> to configure your own `.gitlab-ci.yml`. To do that, please
|
||||
> read through the article [Creating and Tweaking GitLab CI/CD for GitLab Pages](getting_started_part_four.md). New SSGs are very welcome among
|
||||
> the [example projects](https://gitlab.com/pages). If you set
|
||||
> up a new one, please
|
||||
> [contribute](https://gitlab.com/pages/pages.gitlab.io/blob/master/CONTRIBUTING.md)
|
||||
> to our examples.
|
||||
>
|
||||
> - The second step _"Clone it to your local computer"_, can be done
|
||||
differently, achieving the same results: instead of cloning the bare
|
||||
repository to you local computer and moving your site files into it,
|
||||
you can run `git init` in your local website directory, add the
|
||||
remote URL: `git remote add origin git@gitlab.com:namespace/project-name.git`,
|
||||
then add, commit, and push to GitLab.
|
||||
> differently, achieving the same results: instead of cloning the bare
|
||||
> repository to you local computer and moving your site files into it,
|
||||
> you can run `git init` in your local website directory, add the
|
||||
> remote URL: `git remote add origin git@gitlab.com:namespace/project-name.git`,
|
||||
> then add, commit, and push to GitLab.
|
||||
|
||||
## URLs and Baseurls
|
||||
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@ To get started with GitLab Pages, you can either:
|
|||
1. Select **Create from Template**.
|
||||
1. Choose one of the templates starting with **Pages**:
|
||||
|
||||
|
||||
|
||||
|
||||
1. From the left sidebar, navigate to your project's **CI/CD > Pipelines**
|
||||
and click **Run pipeline** to trigger GitLab CI/CD to build and deploy your
|
||||
|
|
|
|||
|
|
@ -34,11 +34,11 @@ that the `master` branch is protected by default.
|
|||
1. From the **Branch** dropdown menu, select the branch you want to protect and
|
||||
click **Protect**. In the screenshot below, we chose the `develop` branch.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Once done, the protected branch will appear in the "Protected branches" list.
|
||||
|
||||
|
||||
|
||||
|
||||
## Using the Allowed to merge and Allowed to push settings
|
||||
|
||||
|
|
@ -145,7 +145,7 @@ branches via GitLab's web interface:
|
|||
1. In order to prevent accidental deletion, an additional confirmation is
|
||||
required
|
||||
|
||||
|
||||
|
||||
|
||||
Deleting a protected branch is only allowed via the web interface, not via Git.
|
||||
This means that you can't accidentally delete a protected branch from your
|
||||
|
|
|
|||
|
|
@ -20,19 +20,19 @@ To protect a tag, you need to have at least Maintainer permission level.
|
|||
|
||||
1. Navigate to the project's **Settings > Repository**:
|
||||
|
||||
|
||||
|
||||
|
||||
1. From the **Tag** dropdown menu, select the tag you want to protect or type and click **Create wildcard**. In the screenshot below, we chose to protect all tags matching `v*`:
|
||||
|
||||
|
||||
|
||||
|
||||
1. From the **Allowed to create** dropdown, select who will have permission to create matching tags and then click **Protect**:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Once done, the protected tag will appear in the **Protected tags** list:
|
||||
|
||||
|
||||
|
||||
|
||||
## Wildcard protected tags
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue