From 12343b6fb235d511d200add23957e9d617ba95dc Mon Sep 17 00:00:00 2001 From: Antoine-Studer <107634121+Antoine-Studer@users.noreply.github.com> Date: Wed, 21 Jan 2026 10:34:13 +0100 Subject: [PATCH] Highlight refactoring step for CI release pipeline Grosse confusion de plusieurs personnes car nous ne savons pas lire --- doc/step4_further_improvements.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/step4_further_improvements.md b/doc/step4_further_improvements.md index 47b7332b..66d0aa92 100644 --- a/doc/step4_further_improvements.md +++ b/doc/step4_further_improvements.md @@ -36,7 +36,7 @@ Every suggested improvements will be followed with clue(s) to achieve it. :star::star: Create the CI Pipeline for releases and connect it to our CD Pipeline -→ At this step, CI release pipeline could just be single or multiple jobs (for both frontend & backend) executed before CD pipeline Jobs. Spliting into two distinct workflows is further refactoring step. +→ At this step, CI release pipeline could just be single or multiple jobs (for both frontend & backend) executed before CD pipeline Jobs. **Spliting into two distinct workflows is further refactoring step**. → The CI release pipeline would (in parallel or sequentially) : - For Frontend app : @@ -92,4 +92,4 @@ If all workflow is trigger by a tag → it should match the following pattern → Solution should keep all previous features -→ Don't forget secrets and azure things ... :eyes: \ No newline at end of file +→ Don't forget secrets and azure things ... :eyes: