Commit 0a2a6686 authored by Mike Lewis's avatar Mike Lewis Committed by Marcia Ramos

Add links to select YouTube videos demonstrating GitLab features to docs

parent c5902f15
...@@ -53,6 +53,8 @@ persist through a commit ID change when: ...@@ -53,6 +53,8 @@ persist through a commit ID change when:
- force-pushing after a rebase - force-pushing after a rebase
- amending a commit - amending a commit
This functionality is also demonstrated in the video [How to use Merge Request Commit Discussions](https://www.youtube.com/watch?v=TviJH6oRboo).
To create a commit diff discussion: To create a commit diff discussion:
1. Navigate to the merge request **Commits** tab. A list of commits that 1. Navigate to the merge request **Commits** tab. A list of commits that
......
...@@ -32,6 +32,8 @@ An issue, epic, or merge request cannot have two scoped labels with the same key ...@@ -32,6 +32,8 @@ An issue, epic, or merge request cannot have two scoped labels with the same key
For example, if an issue is already labeled `priority::3` and you apply the label `priority::2` to it, For example, if an issue is already labeled `priority::3` and you apply the label `priority::2` to it,
`priority::3` is automatically removed. `priority::3` is automatically removed.
This functionality is demonstrated in a video titled [Use scoped labels in GitLab 11.10 for custom fields and custom workflows](https://www.youtube.com/watch?v=4BCBby6du3c).
### Labels with multiple colon pairs ### Labels with multiple colon pairs
If labels have multiple instances of `::`, the longest path from left to right, until the last `::`, is considered the "key" or the "scope". If labels have multiple instances of `::`, the longest path from left to right, until the last `::`, is considered the "key" or the "scope".
......
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