From ba99303f1667dd743004d57d39f8d12eb40de8b9 Mon Sep 17 00:00:00 2001 From: "franz.germann1" Date: Wed, 18 Dec 2024 13:47:10 +0100 Subject: [PATCH] updates image in ci-workflow.md --- docs/userguide/ci-workflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/userguide/ci-workflow.md b/docs/userguide/ci-workflow.md index db431f0..4c8e01e 100644 --- a/docs/userguide/ci-workflow.md +++ b/docs/userguide/ci-workflow.md @@ -2,8 +2,6 @@ Our repository includes a **Continuous Integration (CI) workflow** that runs automatically whenever changes are pushed to the codebase. By leveraging Forgejo and GitHub Actions, we ensure that every update is thoroughly validated, resulting in a reliable and error-free image being delivered to the Forgejo registry. -![step 2](../ressources/5.png) - --- ## How It Works @@ -12,6 +10,8 @@ Our repository includes a **Continuous Integration (CI) workflow** that runs aut Each time you push a new commit or open a pull request, a CI workflow is initiated. You can monitor these runs by navigating to the Actions tab within your GitHub project. +![step 2](../ressources/5.png) + ### Workflow Steps The CI pipeline consists of several predefined steps designed to ensure quality and security before publishing the final image: