From c7509a9c858ffeef9a3868b708b9335c6258618a Mon Sep 17 00:00:00 2001 From: lijunjie Date: Thu, 10 Jan 2019 17:22:36 +0800 Subject: [PATCH] Fix the misspelling of "default" Change-Id: I0a96eebec595ed510abde253a517c4b73cf5ec7b --- ...-and-run-workflows-within-namespaces-e4fba869a889f55f.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/releasenotes/notes/create-and-run-workflows-within-namespaces-e4fba869a889f55f.yaml b/releasenotes/notes/create-and-run-workflows-within-namespaces-e4fba869a889f55f.yaml index 864589052..cf5771c24 100644 --- a/releasenotes/notes/create-and-run-workflows-within-namespaces-e4fba869a889f55f.yaml +++ b/releasenotes/notes/create-and-run-workflows-within-namespaces-e4fba869a889f55f.yaml @@ -7,11 +7,11 @@ features: All existing workflows are assumed to be in the default namespace, represented by an empty string. Also if a workflow is created without a - namespace spcified, it is assumed to be in the defualt namespace. + namespace spcified, it is assumed to be in the default namespace. When a workflow is being executed, the namespace is saved under params and passed to all its sub workflow executions. When looking for the next sub-workflow to run, the correct workflow will be found by name and namespace, where the namespace can be the workflow namespace or the default namespace. Workflows in the same namespace as the top workflow will be - given a higher priority. \ No newline at end of file + given a higher priority.