You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2023/07/14 05:23:41 UTC

[camel-k] 02/03: Chore: indent warning message

This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git

commit 027d55b6b0dc39d4febac1970e3398c1e4db9b83
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu Jul 13 15:37:54 2023 +0200

    Chore: indent warning message
---
 docs/modules/ROOT/pages/pipeline/pipeline.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/modules/ROOT/pages/pipeline/pipeline.adoc b/docs/modules/ROOT/pages/pipeline/pipeline.adoc
index 16af4a9e1..352a9f319 100644
--- a/docs/modules/ROOT/pages/pipeline/pipeline.adoc
+++ b/docs/modules/ROOT/pages/pipeline/pipeline.adoc
@@ -25,7 +25,7 @@ The custom tasks will be executed in the directory where the Camel K runtime Mav
 
 The goal is to let the user perform custom tasks which may result in a success or a failure. If the task executed results in a failure, then, the entire build is stopped and fails accordingly.
 
-WARNING: The custom tasks are only available only when using pod strategy.
+> Warning: The custom tasks are only available only when using pod strategy.
 
 [[build-pipeline-trait]]
 == Configuring via builder trait
@@ -104,4 +104,4 @@ If for any reason you still need to access the entire log of the execution, you
 
 As we are using container registry for execution, you will be able to execute virtually any kind of task. You can provide your own container with tools required by your company or use any one available in the OSS.
 
-As the target of the execution is the project, before the artifact is published to the registry, you can execute any task to validate the project. We can think of any vulnerability tool scanner, quality of code or any other action you tipically perform in your build pipeline.
\ No newline at end of file
+As the target of the execution is the project, before the artifact is published to the registry, you can execute any task to validate the project. We can think of any vulnerability tool scanner, quality of code or any other action you tipically perform in your build pipeline.