From 52617cd7e6db505b25edb4cd6ae23b319c2e1e1d Mon Sep 17 00:00:00 2001
From: "marcoemi.poleggi" <marco-emilio.poleggi@hesge.ch>
Date: Wed, 23 Nov 2022 16:53:21 +0100
Subject: [PATCH] Update README.md

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f9d9e1c..52688d5 100644
--- a/README.md
+++ b/README.md
@@ -58,6 +58,8 @@ Fork this project into your personal namespace and configure it (menu `Settings`
 Our GitLab instance comes with a shared Docker-based CI/CD *runner* (or executor).
 Generate your [SSH key pair](https://docs.gitlab.com/ee/ci/ssh_keys/) to interact with your VM instance.
 
+(**[TO-DO]** :question: Do we also need to enable `Repository > Deploy keys` with the same public SSH key?)
+
 Configure the CI/CD system as it follows (menu `Settings > CI/CD`):
 - In `General pipelines`:
   * [ ] `Public pipelines`
@@ -74,7 +76,7 @@ Configure the CI/CD system as it follows (menu `Settings > CI/CD`):
 
 ### Task #2: CI/CD pipeline ###
 
-**Goal:** write a GitLab-style pipeline file `.gitlab-ci.yml`.
+**Goal:** write a GitLab-style "branch" pipeline file `.gitlab-ci.yml`.
 
 For our simple DevOps scenario, the following structure suffices:
 
-- 
GitLab