Commit fda60ef8 authored by Craig Norris's avatar Craig Norris Committed by Amy Qualls

Move tags file to topics

Move the tags file from university directory.
parent 44b5c7a0
...@@ -42,7 +42,7 @@ The following resources will help you get started with Git: ...@@ -42,7 +42,7 @@ The following resources will help you get started with Git:
- [Git stash](../../university/training/topics/stash.md) - [Git stash](../../university/training/topics/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](../../university/training/user_training.md#tags) - [Git tags](tags.md)
### Concepts ### Concepts
......
---
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/engineering/ux/technical-writing/#assignments
---
# Tags
Tags are useful for marking 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
```
## Additional resources
- [Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging) Git reference page
...@@ -34,7 +34,6 @@ This section contains the following topics: ...@@ -34,7 +34,6 @@ This section contains the following topics:
- [Merge conflicts](topics/merge_conflicts.md). - [Merge conflicts](topics/merge_conflicts.md).
- [Rollback commits](topics/rollback_commits.md). - [Rollback commits](topics/rollback_commits.md).
- [Subtree](topics/subtree.md). - [Subtree](topics/subtree.md).
- [Tags](topics/tags.md).
- [Unstage](topics/unstage.md). - [Unstage](topics/unstage.md).
## Additional Resources ## Additional Resources
......
--- ---
stage: none redirect_to: '../../../topics/git/tags.md'
group: unassigned
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
comments: false
type: reference
--- ---
# Tags This document was moved to [another location](../../../topics/git/tags.md).
- Useful for marking deployments and releases <!-- This redirect file can be deleted after <YYYY-MM-DD>. -->
- Annotated tags are an unchangeable part of Git history <!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->
- Soft/lightweight tags can be set and removed at will
- Many projects combine an annotated release tag with a stable branch
- Consider setting deployment/release tags automatically
## Tags sample workflow
- Create a lightweight tag
- Create an annotated tag
- 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
```
**Additional resources**
<https://git-scm.com/book/en/Git-Basics-Tagging>
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->
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