diff --git a/content/docs/version-control-cicd/cicd/01.github-action.md b/content/docs/version-control-cicd/cicd/01.github-action.md
index 43966dfd40..d48b6a046e 100644
--- a/content/docs/version-control-cicd/cicd/01.github-action.md
+++ b/content/docs/version-control-cicd/cicd/01.github-action.md
@@ -23,7 +23,6 @@ Kestra offers two Actions to create a CI/CD pipeline within a GitHub repository.
 
 Here is an example of a Workflow using the Kestra actions to validate all Flows before deploying them.
 
-
 ```yaml
 name: Kestra CI/CD
 on: [push]
@@ -32,11 +31,14 @@ jobs:
     runs-on: ubuntu-latest
     name: Kestra validate
     steps:
+      - name: Checkout repo content
+        uses: actions/checkout@v4
+
       - name: Validate all flows on server-side
         uses: kestra-io/validate-action@develop
         with:
           directory: ./kestra/flows
-          server: https://kestra.io/
+          server: server_url
           apiToken: ${{ secrets.KESTRA_API_TOKEN }}
 
   # If validation passed, deploy resources
@@ -46,12 +48,15 @@ jobs:
     steps:
       # We can only deploy to one namespace at once,
       # so we have two different steps for our two namespaces product and engineering
+      - name: Checkout repo content
+        uses: actions/checkout@v4
+
       - name: Deploy product flows
         uses: kestra-io/deploy-action@develop
         with:
           namespace: product
           directory: ./kestra/flows/product
-          server: https://kestra.io/
+          server: server_url
           apiToken: ${{ secrets.KESTRA_API_TOKEN }}
 
       - name: Deploy engineering flows
@@ -59,7 +64,7 @@ jobs:
         with:
           namespace: engineering
           directory: ./kestra/flows/engineering
-          server: https://kestra.io/
+          server: server_url
           apiToken: ${{ secrets.KESTRA_API_TOKEN }}
 ```