From 36a42a8d91668acfb091e824af6c46607d408eb5 Mon Sep 17 00:00:00 2001
From: Christopher Ruwisch <christopher.ruwisch@gmail.com>
Date: Tue, 4 Feb 2025 21:40:33 +0100
Subject: [PATCH] update contribute.md using site: ... for merge-request
workflow
---
docs/get-involved/contribute.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/get-involved/contribute.md b/docs/get-involved/contribute.md
index 8ec14b9..cc78b6a 100644
--- a/docs/get-involved/contribute.md
+++ b/docs/get-involved/contribute.md
@@ -20,10 +20,11 @@ This is how you can actually make a difference:
The flowchart below illustrates the Merge Request workflow, along with the commands used at each stage.
<figure>
- <img src="../../assets/images/merge_request_workflow.png" alt="merge-request" width="500" style="border: 2px solid black;">
+ <img src="site:assets/images/merge_request_workflow.png" alt="merge-request" width="500" style="border: 2px solid black;">
<figcaption>Merge request workflow</figcaption>
</figure>
+
You cloned/forked the UNICADO Package successfully acc. to [Get Source Code](get-source-code.md). Nice! You want to make a change, e.g. fixing a bug or creating a new feature, so you create a *issue* (see also [types of contribution](#contributions)). Then you :point_up: create a feature branch, change the code and create a merge request (here a [how to](merge-request.md)). An automatic CI/CD pipeline is triggered, which helps your selected reviewer to make sure that request is ok. If it is accepted and ready-to-land :airplane:, the documentation is automatically updated. Nicely done :+1:
## Types of contribution {#contributions}
--
GitLab