Skip to content
代码片段 群组 项目
提交 f0e776b9 编辑于 作者: Amy Qualls's avatar Amy Qualls 提交者: Susan Tacker
浏览文件

Move the tags page from topics/ to UI directory

If we're about to document more things about tags, we should fish
this page out of the topics directory and put it in the UI hierarchy
where it will (eventually) belong.
上级 23bf7ea1
No related branches found
No related tags found
无相关合并请求
...@@ -281,7 +281,7 @@ Use: ...@@ -281,7 +281,7 @@ Use:
- The `project` keyword to specify the full path to the downstream project. - The `project` keyword to specify the full path to the downstream project.
In [GitLab 15.3 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/367660), In [GitLab 15.3 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/367660),
you can use [variable expansion](../variables/where_variables_can_be_used.md#gitlab-ciyml-file). you can use [variable expansion](../variables/where_variables_can_be_used.md#gitlab-ciyml-file).
- The `branch` keyword to specify the name of a branch or [tag](../../topics/git/tags.md) - The `branch` keyword to specify the name of a branch or [tag](../../user/project/repository/tags/index.md)
in the project specified by `project`. You can use variable expansion. in the project specified by `project`. You can use variable expansion.
## Trigger a multi-project pipeline by using the API ## Trigger a multi-project pipeline by using the API
......
...@@ -43,7 +43,7 @@ The following resources can help you get started with Git: ...@@ -43,7 +43,7 @@ The following resources can help you get started with Git:
- [Git stash](stash.md) - [Git stash](stash.md)
- [Git file blame](../../user/project/repository/git_blame.md) - [Git file blame](../../user/project/repository/git_blame.md)
- [Git file history](../../user/project/repository/git_history.md) - [Git file history](../../user/project/repository/git_history.md)
- [Git tags](tags.md) - [Git tags](../../user/project/repository/tags/index.md)
### Concepts ### Concepts
......
--- ---
stage: Create redirect_to: '../../user/project/repository/tags/index.md'
group: Source Code remove_date: '2023-05-27'
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
--- ---
# Tags **(FREE)** This document was moved to [another location](../../user/project/repository/tags/index.md).
Tags help you mark certain deployments and releases for later <!-- This redirect file can be deleted after <2023-05-27>. -->
reference. Git supports two types of tags: <!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
- Annotated tags: An unchangeable part of Git history. <!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
- Lightweight (soft) tags: Tags that can be set and removed as needed.
Many projects combine an annotated release tag with a stable branch. Consider
setting deployment or release tags automatically.
## Tags sample workflow
1. Create a lightweight tag.
1. Create an annotated tag.
1. Push the tags to the remote repository.
```shell
git checkout master
# Lightweight tag
git tag my_lightweight_tag
# Annotated tag
git tag -a v1.0 -m 'Version 1.0'
# Show list of the existing tags
git tag
git push origin --tags
```
## Related topics
- [Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging) Git reference page
...@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Protected tags **(FREE)** # Protected tags **(FREE)**
Protected tags: Protected [tags](repository/tags/index.md):
- Allow control over who has permission to create tags. - Allow control over who has permission to create tags.
- Prevent accidental update or deletion once created. - Prevent accidental update or deletion once created.
...@@ -106,6 +106,11 @@ Protected tags can only be deleted by using GitLab either from the UI or API. ...@@ -106,6 +106,11 @@ Protected tags can only be deleted by using GitLab either from the UI or API.
These protections prevent you from accidentally deleting a tag through local These protections prevent you from accidentally deleting a tag through local
Git commands or third-party Git clients. Git commands or third-party Git clients.
## Related topics
- [Protected Tags API](../../api/protected_tags.md)
- [Tags API](../../api/tags.md)
<!-- ## Troubleshooting <!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues Include any troubleshooting steps that you can foresee. If you know beforehand what issues
......
...@@ -88,7 +88,7 @@ To create a release in the Releases page: ...@@ -88,7 +88,7 @@ To create a release in the Releases page:
- [Title](release_fields.md#title). - [Title](release_fields.md#title).
- [Milestones](#associate-milestones-with-a-release). - [Milestones](#associate-milestones-with-a-release).
- [Release notes](release_fields.md#release-notes-description). - [Release notes](release_fields.md#release-notes-description).
- Whether or not to include the [Tag message](../../../topics/git/tags.md). - Whether or not to include the [Tag message](../repository/tags/index.md).
- [Asset links](release_fields.md#links). - [Asset links](release_fields.md#links).
1. Select **Create release**. 1. Select **Create release**.
......
---
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Tags **(FREE)**
Tags help you mark certain deployments and releases for later
reference. Git supports two types of tags:
- Annotated tags: An unchangeable part of Git history.
- Lightweight (soft) tags: Tags that can be set and removed as needed.
Many projects combine an annotated release tag with a stable branch. Consider
setting deployment or release tags automatically.
## Tags sample workflow
1. Create a lightweight tag.
1. Create an annotated tag.
1. Push the tags to the remote repository.
```shell
git checkout master
# Lightweight tag
git tag my_lightweight_tag
# Annotated tag
git tag -a v1.0 -m 'Version 1.0'
# Show list of the existing tags
git tag
git push origin --tags
```
## Related topics
- [Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging) Git reference page
- [Protected tags](../../protected_tags.md)
- [Tags API](../../../../api/tags.md)
...@@ -115,7 +115,7 @@ To create a [branch](branches/index.md) in the Web Editor: ...@@ -115,7 +115,7 @@ To create a [branch](branches/index.md) in the Web Editor:
## Create a tag ## Create a tag
You can create [tags](../../../topics/git/tags.md) to mark milestones such as You can create [tags](tags/index.md) to mark milestones such as
production releases and release candidates. To create a tag in the Web Editor: production releases and release candidates. To create a tag in the Web Editor:
1. On the top bar, select **Main menu > Projects** and find your project. 1. On the top bar, select **Main menu > Projects** and find your project.
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册