From 2b7a199f13b2f270021aaf926db0d853cf4375ca Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Thu, 20 Jun 2019 09:20:06 +0000 Subject: [PATCH 1/2] Merge branch 'docs/existing-knative-edit' into 'master' Add version text and edit section See merge request gitlab-org/gitlab-ce!29875 (cherry picked from commit e0125d7bc006d5ccbad9db5258d403071ced674d) 5239f88d Add version text and edit section --- doc/user/project/clusters/serverless/index.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/doc/user/project/clusters/serverless/index.md b/doc/user/project/clusters/serverless/index.md index 0ab6d8e112f..3be5bfeaddc 100644 --- a/doc/user/project/clusters/serverless/index.md +++ b/doc/user/project/clusters/serverless/index.md @@ -85,12 +85,22 @@ on a given project but not both. The current implementation makes use of a `serv ## Using an existing installation of Knative +> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/58941) in GitLab 12.0. + NOTE: **Note:** -The "invocations" monitoring feature of GitLab serverless will not work when adding an existing installation of Knative. +The "invocations" monitoring feature of GitLab serverless will not work when +adding an existing installation of Knative. + +It is also possible to use GitLab Serverless with an existing Kubernetes +cluster which already has Knative installed. + +Simply: -It is also possible to use GitLab Serverless with an existing Kubernetes cluster which already has Knative installed. -Simply follow the steps to [add an existing Kubernetes cluster](../index.md#adding-an-existing-kubernetes-cluster) -and then follow the steps to deploy [functions](#deploying-functions) or [serverless applications](#deploying-serverless-applications) onto your cluster. +1. Follow the steps to + [add an existing Kubernetes cluster](../index.md#adding-an-existing-kubernetes-cluster). +1. Follow the steps to deploy [functions](#deploying-functions) + or [serverless applications](#deploying-serverless-applications) onto your + cluster. ## Deploying functions -- GitLab From 3b1ffeb812161d362a06270ad6f9786c43c649f2 Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Thu, 20 Jun 2019 09:15:40 +0000 Subject: [PATCH 2/2] Merge branch 'docs/edit-zoom-call-link-content' into 'master' Edit new Zoom call link content See merge request gitlab-org/gitlab-ce!29878 (cherry picked from commit 265fc7bc336f061570bab5bd7483b2f86b12ce7f) 52252430 Edit new Zoom call link content --- doc/user/project/issues/issue_data_and_actions.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/doc/user/project/issues/issue_data_and_actions.md b/doc/user/project/issues/issue_data_and_actions.md index ac26b672d99..2103f331aa2 100644 --- a/doc/user/project/issues/issue_data_and_actions.md +++ b/doc/user/project/issues/issue_data_and_actions.md @@ -149,12 +149,19 @@ The plain text title and description of the issue fill the top center of the iss The description fully supports [GitLab Flavored Markdown](../../markdown.md#gitlab-flavored-markdown-gfm), allowing many formatting options. -##### 16.1 Zoom Call Links +##### Zoom call links -Including a link to a Zoom call in the description of an issue will result in a "Join Zoom meeting" button at the top of the issue, just under the header. To remove the button, edit the description and remove the Zoom call link. +> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/62966) in GitLab 12.0. + +Including a link to a [Zoom](https://zoom.us) call in the description of an issue +results in a **Join Zoom meeting** button at the top of the issue, just under the header. + +For example: ![Link Zoom Call in Issue](img/link_zoom_call_in_issue.png) +To remove the button, edit the description and remove the Zoom call link. + #### 17. Mentions You can mention a user or a group present in your GitLab instance with `@username` or -- GitLab