diff options
| author | Jason Lenny <jlenny@gitlab.com> | 2019-01-03 15:08:16 +0000 |
|---|---|---|
| committer | Jason Lenny <jlenny@gitlab.com> | 2019-01-03 15:08:16 +0000 |
| commit | 9c3c1479427115ffb212d50799a1ac653b988850 (patch) | |
| tree | 5fb3abc3a064852921c11e2c2b1309e5d380e3f2 | |
| parent | 55655cfd30b794cd8bca712654bca1b08f057e83 (diff) | |
| download | gitlab-ce-9c3c1479427115ffb212d50799a1ac653b988850.tar.gz | |
Fix documentation links
| -rw-r--r-- | doc/user/project/releases.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/releases.md b/doc/user/project/releases.md index 34889ecf982..1edb26e9642 100644 --- a/doc/user/project/releases.md +++ b/doc/user/project/releases.md @@ -2,7 +2,7 @@ > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/41766) in GitLab 11.7. -It's typical to create a [git tag](doc/university/training/topics/tags.md) at +It's typical to create a [git tag](https://docs.gitlab.com/ee/university/training/topics/tags.html) at the moment of release in order to create a checkpoint in your source code history, but in most cases your users will need compiled objects or other assets output by your CI system in order to use them, not just the raw source @@ -23,7 +23,7 @@ your users to quickly scan the differences between each one you publish. NOTE: **NOTE** - [Git's tagging messages](https://git-scm.com/book/en/v2/Git-Basics-Tagging) and release descriptions are unrelated. -- Description supports [markdown](doc/user/markdown.md) +- Description supports [markdown](https://docs.gitlab.com/ee/user/markdown.html) ## Assets of a release |