Michal.Wrobel/edp-doc
1
0
Fork 0
forked from DevFW-CICD/edp-doc
Code Pull requests Activity

updates image in ci-workflow.md

Browse source
This commit is contained in:
franz.germann1 2024-12-18 13:47:10 +01:00
parent ee1101fb3a
commit ba99303f16
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/userguide/ci-workflow.md
View file

@ -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. 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 ## 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. 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 ### Workflow Steps
The CI pipeline consists of several predefined steps designed to ensure quality and security before publishing the final image: The CI pipeline consists of several predefined steps designed to ensure quality and security before publishing the final image: